-
Data files are being written with 32 bit depth even when data collected at 16 bit depth, this is causing zocalo issues with wrong max pixel values. The "correct" bit depth is now included in the meta …
-
As a developer I would like to be able to easily see a number of things about my plans, plan stubs and devices:
* When was the last time this was used
* Which beamline was it used on - maybe even wh…
-
I observed that while looping over a set of parameters (e.g. focus position) doing beamline setup and propagation (day one configuation for spb/sfx), memory occupation just goes up, eventually hitting…
-
Should the `instrument_view` be removed altogether? I see it's use could be quite limited if we are adding instrument-specific versions in the other packages (e.g. `dream.instrument_view`).
There i…
-
This is a suggestion for adding an optical element that acts like a screen. It can be used to dump the wavefront at the screen's position to a file. In this way, we could trace the the WF as it propa…
-
I am trying to use a mode file to do a partially coherent calculation for a KB beamline.
I try to use one of the existing mode files
However I get the message: "Simulation Error: An unknown error oc…
bnash updated
2 years ago
-
## Overview
We need to handle metadata in a few places. And some of that metadata is common to many techniques and workflows. In particular, we may/will have SciCat metadata in many workflows. But …
-
Rename creationLocation to beamline-or-instrument and make it optional (especially for private logbooks).
Also users should be allowed to come up with new values (i.e. names) for these keys when a…
-
## Expected Behavior
In our LCLS happi schema, force names like XPP, LFE, MFX for the beamline field
## Current Behavior
Allows names like xpp, lfe, mfx
## Context
Naming consis…
-
It could be helpful to have pre-built UI in Python packages for easier deployment. This should be investigated.