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
I would like to request an added StartCapture option, -t, which suppresses GMN checking for revised .config, mask or platepar. This option would only be used for short test captures on a .config that is already set to upload: false.
Or, even better, if upload_enabled: false, then suppress checking for revised files, since this would not require a new cmd line option.
Without this capability a test with -d 0.03 spends more time timing out, while waiting for new files, than it does actually running the test capture and processing.
Thanks,
Peter E.
The text was updated successfully, but these errors were encountered:
peschman
changed the title
StartCaptue option to suppress checking GMN for revised platepar & mask
StartCapture option to suppress checking GMN for revised platepar & mask
Aug 18, 2024
Interesting thought. I don't like the idea of skipping the checks for updated files if upload is false, because at least two operators, and multiple stations do not use the standard RMS upload mechanism, and have upload_enabled set to false. I think you are referencing a special case where your private key does not match the public key of the account you are trying to connect to.
Given the problems that might be caused by relying on upload_enabled: false, I think the -t or other char to indicate running in test mode would be the best solution. This would allow test runs to complete without having to wait for comms timeouts when looking for new mask or platepar on GMN.
I would like to request an added StartCapture option, -t, which suppresses GMN checking for revised .config, mask or platepar. This option would only be used for short test captures on a .config that is already set to upload: false.
Or, even better, if upload_enabled: false, then suppress checking for revised files, since this would not require a new cmd line option.
Without this capability a test with -d 0.03 spends more time timing out, while waiting for new files, than it does actually running the test capture and processing.
Thanks,
Peter E.
The text was updated successfully, but these errors were encountered: