tub-rip / cocapture Goto Github PK

There seems to be a mismatch between the selected slider position for 'bias_diff_off' in ImGui and in the camera. The sliders for the other bias values work fine

Build is failing on main branch.
Lines 28-29 are repeated in lines 47-48 in prophesee_cam.cpp.

At the end of a recording (stop button pressed), a sanity check should be performed assuring that the number of frames captured with a Basler camera equals the number of trigger events.
Sanity check should only be performed when recording with a Basler camera and a prophesee camera.

Requirement:

• Option for User (can be at startup) to flip the view of a camera horizontically or vertically

As some downstream task require trigger events but might not have access to them through the .raw file it would be good to write them to a separate .txt file in the recording directory for now. Like so:

https://github.com/friedhelm-h/rip-co-capture/blob/main/cpp/src/trigger_event_saver.cpp

@sfilbertf: I know we talked about it before and did not do it but it seems useful now as some packages used for reading the .raw file do not support reading trigger events

Hi.
Are you loading default bias values from the devices when the recorder in launched? The events look very sparse, and highly imbalanced (events of one polarity outnumber the other). Here is a snapshot for reference.

I checked in metavision_studio that all bias values are set to 0 by default. which looks ok.

So, here are some things that need to changed:

1. Could be make the range of values bigger, at least on the lower side, so that contrast sensitivity can be increased?
2. Could we set default bias values such that they match the metavision_viewer or metavision_studio? This should fix the sparseness and imbalance.
3. Can we add a legend in the side-panel to identify which color represents which polarity?

At the moment hard coding of serial numbers is required on start-up

Hi, I have a question.

Is there a way to detect the loss of recorded events or saturation of timestamps for the Prophesee cam recorder?
Just binary (recording droppedor similar) is fine for now.
If I remember correctly, Friedhelm has it for Basler recording, if any frames are dropped during the recordings.
So I'm wondering if you already have the similar one for the Prophesee.
Thanks!

Hi. I am not sure if this is already possible, but it would be nice if while launching even a single event camera, we could specify whether we want to start it in master or slave mode. This would enable us to use multiple laptops for recording synchronized data.

Additionally, it would be good to explicitly mention by serial ID when we starting the cameras, and specify which camera we want to be in master mode while launching in a stereo configuration. I believe that at the moment, it is fetching the first available camera.

Hi, what is the meaning of

Opening Prophesee Camera: Prophesee:hal_plugin_gen41_evk3:00042177
Set mode Master successful.Remember to start the slave first.

After I started the ./recorder --cameras prophesee ?