Can the energy scan plan window pass in the name of the edge (e.g. Ni-K) instead of the E0 value itself?
The energy plan window allows you to specify E0 using an editable combobox by either typing an explicit energy (e.g. 8333.0), or by selecting a named edge from the list (e.g. Ni K (8333 eV)).
The energy_scan() plan creates two metadata keys: "edge" and "E0". If the plan is called as energy_scan(..., E0="Ni-K") then the metadata become:
{
"edge": "Ni-K",
"E0": 8333.0,
}
and if called as energy_scan(..., E0=8333.0) then the metadata are:
{
"edge": 8333.0,
"E0": 8333.0,
}
Since the Firefly energy_scan plan window converts the edge name to its energy value before creating the BPlan object, the latter metadata are saved.
If we modify the plan window to pass the edge name, then we get a few benefits.
It is clear in the run browser which element is being measured.
We can search the database for all Nickel edges
We can include these keys in the NeXuS file when exporting
Can the energy scan plan window pass in the name of the edge (e.g.
Ni-K) instead of the E0 value itself?The energy plan window allows you to specify E0 using an editable combobox by either typing an explicit energy (e.g.
8333.0), or by selecting a named edge from the list (e.g.Ni K (8333 eV)).The
energy_scan()plan creates two metadata keys: "edge" and "E0". If the plan is called asenergy_scan(..., E0="Ni-K")then the metadata become:and if called as
energy_scan(..., E0=8333.0)then the metadata are:Since the Firefly energy_scan plan window converts the edge name to its energy value before creating the
BPlanobject, the latter metadata are saved.If we modify the plan window to pass the edge name, then we get a few benefits.