The /Equipment/ZFC odb path is hardcoded in multiple places in this frontend. However, that path was renamed to /Equipment/Zero_field_compens on VMS.
It is likely that this causes the frontend to fail.
The /Equipment/ZFC odb path is hardcoded in multiple places in this frontend. However, that path was renamed to /Equipment/Zero_field_compens on VMS.
It is likely that this causes the frontend to fail.
https://gitea.psi.ch/lin-midas-drivers/expmag/src/commit/b7b388216370214333d2ac7bd17b46d4e2c70d5b/device/expmag.cxx#L3876
@wall_e As a hotfix, I think I can just replace the corresponding ZFC paths with the new VMS variant. However, since this frontend is also used on GPS and GPD, this might create issues, when the previous ZFC device is renamed to something else there.
Should I go ahead with that anyway, for now? Or aim for something more configurable?
@wall_e As a hotfix, I think I can just replace the corresponding ZFC paths with the new VMS variant. However, since this frontend is also used on GPS and GPD, this might create issues, when the previous ZFC device is renamed to something else there.
Should I go ahead with that anyway, for now? Or aim for something more configurable?
Go ahead for now. It is better that it can be tested with hardware at one of the instruments. We can worry about making it more generic when the beam is back on :D
Go ahead for now. It is better that it can be tested with hardware at one of the instruments. We can worry about making it more generic when the beam is back on :D
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The /Equipment/ZFC odb path is hardcoded in multiple places in this frontend. However, that path was renamed to /Equipment/Zero_field_compens on VMS.
It is likely that this causes the frontend to fail.
@wall_e As a hotfix, I think I can just replace the corresponding ZFC paths with the new VMS variant. However, since this frontend is also used on GPS and GPD, this might create issues, when the previous ZFC device is renamed to something else there.
Should I go ahead with that anyway, for now? Or aim for something more configurable?
Go ahead for now. It is better that it can be tested with hardware at one of the instruments. We can worry about making it more generic when the beam is back on :D