You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At the moment, extra-geom can read CrystFEL geom files and produce valid geometries for several types of detectors. However, there are cases when one may need more generic representation than a predefined detector (e.g. for simulation purposes, or for the detector that is not yes supported by extra-geom). That's why it might be useful to have a generic class geometry loaded from an arbitrary CrystFEL file.
What is needed:
Detecting how many tiles per module
Finding data shapes (frag_ss_pixels, frag_fs_pixels, expected_data_shape)
Defining 3 methods which are not implemented in the base class (split_tiles, _tile_slice, _module_coords_to_tile)
Possibly, retrieving additional information like:
an arbitrary pixel size (res[olution] in CrystFEL terms)
an arbitrary data storage source (other than /entry_1/instrument_1/detector_1/data)
detector distance (clen in CrystFEL terms)
photon_energy
reading from an arbitrary CrystFEL .geom file with from_crystfel_geom must return meaningful information. In case of known detectors (i.e. already supported by extra-geom) it should produce an equal geometry object.
The text was updated successfully, but these errors were encountered:
an arbitrary data storage source (other than /entry_1/instrument_1/detector_1/data)
This is one place where there's a conceptual difference - .geom files describe how to load the data from a file, whereas EXtra-geom doesn't deal with loading data.
Just to record: the initial version of this was released in version 1.3 (docs). Reading CrystFEL geometry files into this generic class has been postponed for now. We'll leave this issue open for that.
I've separately started work on preserving extra info when reading a .geom file and writing it back (branch crystfel-geom-metadata) - I need to get back to this and finish it up.
At the moment,
extra-geom
can read CrystFELgeom
files and produce valid geometries for several types of detectors. However, there are cases when one may need more generic representation than a predefined detector (e.g. for simulation purposes, or for the detector that is not yes supported byextra-geom
). That's why it might be useful to have a generic class geometry loaded from an arbitrary CrystFEL file.What is needed:
frag_ss_pixels
,frag_fs_pixels
,expected_data_shape
)split_tiles
,_tile_slice
,_module_coords_to_tile
)res
[olution] in CrystFEL terms)data
storage source (other than/entry_1/instrument_1/detector_1/data
)clen
in CrystFEL terms)photon_energy
.geom
file withfrom_crystfel_geom
must return meaningful information. In case of known detectors (i.e. already supported byextra-geom
) it should produce an equal geometry object.The text was updated successfully, but these errors were encountered: