discussion about scan_info
looking at scan_info
there are some questions/remarks based on a discussion with @denolf. Here are two scan_info
s (only relevant part) for two different scans that we will base the discussion on
BLISS [53]: s=dmesh(roby,0,1,10,robz,0,1,10,.1,diode)
BLISS [54]: pprint( s.scan_info)
{
'acquisition_chain': {'axis': {
...
'master': {
'scalars': ['axis:roby',
'axis:robz'],
...
}
},
'data_dim': 2,
'npoints': 100,
'npoints1': 10,
'npoints2': 10,
'start': [1.0, 2.0],
'stop': [2.0, 3.0],
'title': 'dmesh roby 0 1 10 robz 0 1 10 0.1',
'type': 'dmesh',
...
}
BLISS [55]: s=a2scan(roby,0,1,robz,0,1,10,.1,diode)
BLISS [56]: pprint( s.scan_info)
{
'acquisition_chain': {'axis': {
...
'master': {
'scalars': ['axis:roby',
'axis:robz'],
...
}
},
'npoints': 10,
'start': [0, 0],
'stop': [1, 1],
'title': 'a2scan roby 0 1 robz 0 1 10 0.1',
'type': 'a2scan',
...
}
here are some questions:
- why is the 'data_dim' entry not alwas there?
- what defines to which axis the entries in 'start' and 'stop' correspond? is it always the same order as 'scan_info['acquisition_chain']['axis']['master']['scalars']'?
- while 'start' and 'stop' are lists, why
npoints1
,npoints2
... are not also in a single list (⚠ it is clear that npoints# is linked to the dimension of the scan and not to number of axis as it is the case forstart
andstop
) - could
'display_names'
be an entry ofscan_info
(see #779 (closed) and #922 (closed))?