Metadata errors to fix

[alexpiet]

Rig

• [x] Rig ID uses YYYYMMDD, not YYYY_MM_DD
• [x] Tube manufacturer should be CUSTOM or OTHER, not null
• [x] Motorized stage needs a model name
• [x] Reward spouts needs a manufacturer. CUSTOM, OTHER, JANELIA
• [x] Solenoid - manufacturer, model, serial number?
• [x] How is there a lick_sensor_type without a lick_sensor?
• [x] Isn’t the lick_sensor the janelia lick detector rather than the spout?
• [x] Speaker Manufacturer, model, serial number?
  • [x] Need info
• [x] Camera lens:
  • [x] How is there a model number without a manufacturer?
  • [x] Do we need to change the focal length field if it doesn’t work for the lens?
• [ ] Add position of cameras
• [ ] Add enclosure
• [ ] Harp daq:
  • [ ] core_version for each harp device, should get dynamically from the devices. I hard-coded the value used in 447.
• [x] Calibrations: typo in lack spout right description
• [x] Beamsplitter:
  • [x] Confirm height of beamsplitter (24 or 25)
  • [x] This is more a choice thing, but if the notes contain “493/574 nm BrightLine dual-edge standard epi-fluorescence dichroic beamsplitter" then I would use a name like “beamsplitter” rather than duplicating half that information in the name. If these are details we want to track, let’s get it into the schema.

Session

• [x] Daq device names don’t match the names in the rig
• [ ] Dynamic foraging task software should be in the stimulus_epoch section
  • there are different stimulus_epoch (auditory or optogenetics). Which one to store the software?
• [x] Speaker name doesn’t match the name in rig
• [ ] How was there 343 uL water consumed in the session and none in the stimulus epoch?
  • I think it makes more sense to store the water in the session instead of a specific stimulus (we have different stimulus auditory tone occurs every trial, optogenetics occurs in some trials...).
• [ ] You list several patches, only one is listed in the Rig (and not with this name)
• [ ] These are surgically implanted fibers I assume?
• [ ] Add Behavior parameters in the stimulus software's parameters fields in the stimulus epoch.

[alexpiet]

@XX-Yin Can you take care of the Session metadata updates?

[XX-Yin]

@XX-Yin Can you take care of the Session metadata updates?

I can handle the session metadata.

[hagikent]

I saw a couple behavior_json has erroneous entries such as animal_weight_post = 24..12 (should reas 24.12) Would it be possible to "force" input type?

This causes ValueError: could not convert string to float and would be a reason for session.json not being produced.

[XX-Yin]

I can add a format check when using the animal_weight_post in the session metadata. Please let me know if you find other edge cases.

[XX-Yin]

I saw a couple behavior_json has erroneous entries such as animal_weight_post = 24..12 (should reas 24.12) Would it be possible to "force" input type?

This causes ValueError: could not convert string to float and would be a reason for session.json not being produced.

This session should be an old session. The current GUI will check the format and the non-numeric expression is not allowed.