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
Ha, I didn't realize you were getting this. I just wrote it as a todo for me. But now that I have you, you can give an opinion.
The system is:
listener computer makes folders on acquisition computer.
user drops files into those folders
lugaro retrieves files from those folders
Problem: Lugaro should not retrieve files while someone else is trying to acquire.
Proposed solution: Lugaro gets triggered to start the whole retrieving/processing at some later time (e.g. 10PM), presumably a script like your archiving one runs and calls "matlab filename" on any files I write into a specified location
Problem the second: If this hypothetical scenario is true - that a second user was acquiring after the first, thus requiring lugaro to wait to transfer - then there are going to be two (or more) users' worth of data on the acquisition computer to be retrieved and processed, so lugaro should do them serially rather than trying to trigger them all at once (if nothing else to avoid GPU usage conflicts, but possibly also hard drive space issues).
Solution to problem 2? Script can tell when matlab returns from the first call?
No description provided.
The text was updated successfully, but these errors were encountered: