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
Adding last two FicTrac-v2 columns to get saved into FlyVR. FicTrac-v2 outputs a .dat file that has 25 columns, but in flyVR2 .h5 file, the last 2 columns are not being saved.
I can add this feature but it will take a bit more than modifying the Python source code. See the python side of things here: https://github.com/murthylab/fly-vr/blob/master/flyvr/fictrac/shmem_transfer_data.py. FicTrac is a C++ program that is loosely coupled with FlyVR. Essentially, we have modified FicTrac to copy its state (the 23 fields) into a special region of shared memory. FlyVR spins up a process that peeks (protected by a semaphore) at this memory periodically to see if the state has changed. The values you see in the HDF5 file will be the values that were recorded in realtime from fictrac via this shared memory connection. I will need to add a small bit of code to fictrac to copy these additional fields. I will then need to handle the Python side of things so that things don’t break in the FicTrac1 case. This might not be too hard since we are just appending to the data structure. Anyway, the only reason I mention all these details is to explain why it might take me more than a few minutes to add this feature.
The text was updated successfully, but these errors were encountered:
Adding last two FicTrac-v2 columns to get saved into FlyVR. FicTrac-v2 outputs a .dat file that has 25 columns, but in flyVR2 .h5 file, the last 2 columns are not being saved.
I can add this feature but it will take a bit more than modifying the Python source code. See the python side of things here: https://github.com/murthylab/fly-vr/blob/master/flyvr/fictrac/shmem_transfer_data.py. FicTrac is a C++ program that is loosely coupled with FlyVR. Essentially, we have modified FicTrac to copy its state (the 23 fields) into a special region of shared memory. FlyVR spins up a process that peeks (protected by a semaphore) at this memory periodically to see if the state has changed. The values you see in the HDF5 file will be the values that were recorded in realtime from fictrac via this shared memory connection. I will need to add a small bit of code to fictrac to copy these additional fields. I will then need to handle the Python side of things so that things don’t break in the FicTrac1 case. This might not be too hard since we are just appending to the data structure. Anyway, the only reason I mention all these details is to explain why it might take me more than a few minutes to add this feature.
The text was updated successfully, but these errors were encountered: