Closed keenanlang closed 8 years ago
saveData.req is not an autosave-request file. The file extension is unfortunate. We could change it, but that might be a problem for folks upgrading IOCs
In XXX, instead of relying on the default, I can define REQ_FILE to be "$(SSCAN)/sscanApp/Db/saveData.whatever", that should make it clear that if they want to use their saveData.req file they'll need to set the macro to that file.
Users will nearly always want to modify saveData.req, because it includes a list of the PVs to be saved for every scan. It might be a good idea to split out the list of PVs into a separate file, and treat the remainder of saveData.whatever as you suggest. (This is planned, in fact, though it's been on the bottom of the pile for a long time. The intended benefit is to allow users to modify and reload the save-PV list at run time.)
Will leave saveData.req where it is currently.
The sscan.iocsh script loads saveData.req by default. We should have a default copy to be found in the db directory and if the user wants to customize, they can just put a copy in their IOC and the new req file will be found first due to the IOC's directories being higher in the requestfile_path search.