CN TODO: expose 'revision' as argument

[CodyCBakerPhD]

In all camera related interfaces, expose control over the explicit 'revision' value used (latest might not be the current 'released' or approved ones for use)

https://github.com/catalystneuro/IBL-to-nwb/blob/main/ibl_to_nwb/datainterfaces/iblposeestimationinterface.py#L44

[CodyCBakerPhD]

@grg2rsr Can you please confirm if the pose estimation data (DLC applied to camera data) is the only data stream for which exposing the 'revision' argument is needed?

Related PR #86

[grg2rsr]

no, this should apply to all processed data. Essentially, we want to be able to tell the ONE object which data of which revision to get.

[CodyCBakerPhD]

Essentially, we want to be able to tell the ONE object which data of which revision to get.

So it should be passed to essentially any call of one.load_object?

no, this should apply to all processed data.

Including wheel?

Spike sorting?

Atlas?

Can you show a quick snippet of it for the SpikeSortingLoader?

[grg2rsr]

I doubt that the wheel data is going to change from here on, but the spike sorting might be repeated as spike sorting algorithms will continue to be developed.

the load_spike_sorting function of the SpikeSortingLoader should simply support revision as an argument link.

I will get back to you regarding the atlas