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
A severe weakness of not having things in this library organized into clear classes/organized using OOP is that it becomes quite hard to properly assign new variables/designs.
As discussed here, DA sensor recordings are currently named gcamp recordings because:
Metadata files don't have a great way of encoding it
bruker_control doesn't have a way for understanding a DA sensor
It could be simple enough to add parameters like:
z_stack
t_series
For different indicators. Meaning there would be a function that would determine which z-stacks to collect and iterate through those if the field is true in the yml file. This could be further extended into the t-series recordings as well for if users ever wanted to do dual color imaging.
It's pretty unlikely this will be implemented before the library dies. But it's a good idea anyways.
The text was updated successfully, but these errors were encountered:
A severe weakness of not having things in this library organized into clear classes/organized using OOP is that it becomes quite hard to properly assign new variables/designs.
As discussed here, DA sensor recordings are currently named
gcamp
recordings because:bruker_control
doesn't have a way for understanding a DA sensorIt could be simple enough to add parameters like:
z_stack
t_series
For different indicators. Meaning there would be a function that would determine which z-stacks to collect and iterate through those if the field is
true
in the yml file. This could be further extended into the t-series recordings as well for if users ever wanted to do dual color imaging.It's pretty unlikely this will be implemented before the library dies. But it's a good idea anyways.
The text was updated successfully, but these errors were encountered: