pycroscopy / pycroscopy/asyncroscopy

Covalent use-case: Clarification on what is needed and what not (asyncroscopy relevant details)

Open
#103 6 comments 0 reactions 1 assignee View on GitHub

@Darel-Pates is already working on this.

Since Jun 8, 2026.

Dominant language
Jupyter Notebook
Stars
9
Forks
11
Avg merge
1d 8h
Merged PRs (30d)
2

Description

  • No .h5 support (DataWriter.py): https://github.com/pycroscopy/asyncroscopy/blob/main/asyncroscopy/software/DataWriter.py

    • Client requires .tiff output directly from AS:

      adorned.save("filename.tiff")
      
  • No stack handling for this use case.

  • Tiled integration is not a preference but doesn't hurt

  • Code developed for Talos should ideally run on JEOL as well.

    • This aligns with Asyncroscopy's microscope-agnostic design.
  • Background logging of instrument state (e.g., every 3 seconds) without interrupting user operation.

    • Stage position (X, Y, Z, tilt/rotation angles)
    • FOV
    • Camera angle
    • Scan rotation
    • Defocus
    • Camera length
    • Accelerating voltage
    • Exclude parameters that are not always available or require user interaction (e.g., screen current, as the screen may be retracted).
  • Will update as additional requirements as they emerge.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.