matchings
commented
11 months ago Closing because data release will occur via Code Ocean going forward. Mistargeting of FOV will be a controlled language tag that external users can use to filter out mismatched experiments.
Description of needed information Occasionally an optical physiology field of view is mistargeted, either because the operator errantly went to the wrong location, or because they could not return to the same cells. In these cases, if the experiment & session would otherwise pass, what is the strategy for performing a retake or for keeping the data and releasing it (perhaps not part of the container but something else?)
Are there particular sessions that require a retake but not others?
This does not necessarily block qc but it could halt or slow down the progress of a mouse through the task if a clear strategy is not created.
Also the decision to keep data but disassociate it from a particular container probably has implications for how data is saved in LIMS as well as how it is processed through Mouse-seeks.
Related issues This is somewhat related to issue #13
Describe the solution you'd like Project leads to create a strategy or decision tree that can be used by those collecting data to determine how to move a mouse through it's imaging sequence. It should be clear and concise and easily interpretable.
Alternately assigning a point of contact or a scientist who will make these decisions in a very timely manner so as not to halt a mouse's progression would not be as ideal but would be a functional solution.
Scope This would impact all phase IV projects that have pipeline data collection from RA's, and also have precise targeting or FOV matching requirements.