Closed samiamseid closed 7 months ago
@samiamseid @seanmcculloch Is this a mouse-QC issue or a LIMS issue? It seems like this should be high priority as I think it likely blocks important processing and QC steps
i believe it is a mouse-qc issue. a couple weeks ago Sean did something that briefly got the containers to regenerate, but they stopped again. example mouse 661749
Just wanted to update this with the comment that there are 3 particular mice that dont seem to generate containers. I've tried deleting the cube records from MongoDB and then re-entering the line in the datacube for these mice, but mouse_qc simply does not generate new containers. 661749 647715 644972
These are OpenScopeDendriteCoupling mice that have been stuck in my mouse-closing queue since May because i'm unable to QC the containers in LIMS
@seanmcculloch @samiamseid is this still a problem? i assume it is resolved by now. If so, we should close the ticket
I'm still having the issue mentioned in the previous comment, but the original issue has been resolved. I can make a new ticket if preferred?
I'm not sure why these needed a nudge but containers have been generated. Directly contacting Sam that these mice are ready for closing!
Describe the bug I added mouse ID 662470 to the OpenscopeDendriteCoupling datacube and it is not generating the expected containers. I've also had other issues trying to get containers to repopulate for some mouse-closing, so i suspect something is amiss with container generation in general.
Expected behavior containers should generate based on datacube entrees