cameleon
cameleon copied to clipboard
[WIP] Add support for GIgE cameras
fix #63
- [ ] Check
test_all.sh
is passed. - [ ] Add
fix #{ISSUE_NUMBER}
if the corresponding issue exists. - [ ] Fill out
## Changelog
section. If the change is for only internal use, please writeNone
to the section.
Changelog
Hi @Y-Nak,
Thanks for the work on this library!
Is this GigE support branch still in the roadmap? In addition is the purpose of the library to provide an FFI interface for GenTL producers (like harvester, or implement a native generic producer (like aravis). From a quick review it looks like the FFI approach, will there be a way to manage several different GenTL.cti producers?
Hi @osiler, thanks for your interest!
Yes, it's still on the roadmap! I was quite busy in the last year (new job, relocation to Germany, etc). But yeah, I'm still motivated to finish the GigE camera implementation. I'm still busy now, but I feel like I can restart working on it in two or three months.
The purpose of the GenTL implementation is to simply give access to the cameleon via GenTL API.
will there be a way to manage several different GenTL.cti producers?
No, so far. Cameleon can be regarded as a GenTL producer, so there is no plan to manage the different producers in cameleon.
Ok great, so to summarize the cameleon crate will hopefully allow a drop in open source replacement for GenTL producers that are generally provided by hardware manufactures, while also allowing you to create your own GenTL consumers (clients and software).
Yes, it's 100% correct. One of the main purposes of the crate is to let us be free from vendor lock-in.
No, so far. Cameleon can be regarded as a GenTL producer, so there is no plan to manage the different producers in cameleon.
I was under the impression that was on the roadmap for v0.3.0
, but maybe I misunderstood something.
I deal with a few 3D camera manufacturers that provide GenTL layers as a means of producing disparity maps on the PC's gpu, so integration with vendor cti
files could be useful.
"Add support for GenTL
" on the roadmap means making cameleon a GenTL
producer, not a GenTL
consumer.
So I don't have a plan that users can use GenTL via cameleon; rather, my plan is to allow users to use cameleon via GenTL interfaces.
@Y-Nak, just looking at the contributing guide and for some first issues to help me understand the crate so I can potentially help out. In particular I would be interested in the GigE protocols however I have not implemented / contributed to a protocol before. What do you think the best way to proceed is?