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
Since we now create the manifest file at the start of the session, if a session does not complete a single trial, then it will not have any data to upload (so we don't care about it), and there will be no metadata files (so it won't upload).
In this case we should simply delete the manifest file. We don't have a policy of when we delete data of the acquisition computer, so that isn't a problem yet.
We probably want to implement this as a stand alone script that we set up with Task manager.
Once a day, at like 8pm, we check if all the manifests have the .json file that stores all the data. If not, delete the manifest. We probably should also check that the .json file contains trials.
Alternatively, we could just check when the session ends. If no trials completed, delete the upload manifest. (I think this it the better option)
We could potentially wait to implement this. Its not clear to me how often this happens
The text was updated successfully, but these errors were encountered:
context: I think what is happening is users are stopping the session because the mouse ID is wrong. 100% of the time this happens, the mouse ID has been entered wrong
Since we now create the manifest file at the start of the session, if a session does not complete a single trial, then it will not have any data to upload (so we don't care about it), and there will be no metadata files (so it won't upload).
In this case we should simply delete the manifest file. We don't have a policy of when we delete data of the acquisition computer, so that isn't a problem yet.
We probably want to implement this as a stand alone script that we set up with Task manager.
.json
file that stores all the data. If not, delete the manifest. We probably should also check that the .json file contains trials.The text was updated successfully, but these errors were encountered: