#apertus IRC Channel Logs

Greets.

off for a nap ... bbl

back now ...

off for dinner, bbs

back now ...

hi anuditverma

it is 10:32pm here

BAndiT1983: you here as well

great, maltefiala?

but so far I think there is nothing confidential

well lets start without maltefiala, he might turn up soon

(please avoid Beta access details on the logged channel :)

but all the credentials are exchanged over email already

great

tx, appreciated :)

lets hope malte joins us soon

One thing I wanted to ask, as the beta is connected to a 24X7 machine so as I would pass any parameter updates so the output will be returned to my terminal (of course, I think) but I won't be able to see the beta in action like moving parts and all, in that case it would require a video feed too, so the update feeds on my terminal are fine for now ?

and pipe them into a file to ddownload/convert or analyse remotely

alright, got it

hej there

many things are still missing, but it can already distinguish between different settings, so we can implement different processors for each type

feedback channel is not there yet, but i read something about half-closing the socket for that

so while you can capture images I expect them to be all black

i think that image capturing is less important currently, we have to get other things running, before real tests can be done

Alright, so regarding the task

You sent us a suggestion for a timeline and I think it's good we should go for it

what will be used for REST?

which language do you start with? as there were some on the list

We decided to use go as mentioned in T723

is it updated with the proposal list?

according to my timeline , I would start with Go lang to build a basic client app

how long would it take to develop this app?

@anuditverma, could you link the timeline, is that ok for you

I suggest we stick to the timeline

i will also take a look how Go can be used with C/C++ bindings

@BandiT1983, last time I talked to @Bertl he suggested to use Sockets with JSON to exchange messages instead of a C lib, what do you think?

socket is already there

but then the client has to be done in Go, my intention was to give general C client lib to be used by many languages

thanks

@se6astian Thanks

renamed to https://github.com/apertus-open-source-cinema/axiom-beta-rest-interface

@BAndiT1983, I thought so too at first but @Bertl mentioned it may be sufficient to just provide a socket and exchange json as this may be easier

i use flatbuffers as they are really small

you can see it here -> https://github.com/apertus-open-source-cinema/beta-software/blob/master/axiom_beta_control_daemon/Schema/axiom_daemon.fbs

https://github.com/apertus-open-source-cinema/beta-software/blob/master/axiom_beta_control_daemon/API/ClientExample.cpp

this is how client is sending data at the moment

Go has native support for flatbuffers as far as I know so no need for an extra lib if we can access the socket

but if we need another language, we have to reimplement the functionality

What do you think?

*lense

that was the idea behind universal C clint lib, so any other language with C support could use it without replicating the functionality over and over

client.h provides an interface to supply settings which will be sent as a package, otherwise the user would have to create the right flatbuffer package himself, which is not simple by times

https://github.com/apertus-open-source-cinema/beta-software/blob/master/axiom_beta_control_daemon/API/Client.h

I am ok with either options (C lib or just flatbuffers)

i will still continue to develop the C/C++ client, as i need some test platform

Because @anuditverma s task is doing the go rest interface

a lot is missing as it was just a prototype, but the base works already, just no real connection to camera and daemonization yet, which are the biggest things misssing

don't know what fuzz is about? no pun intended

it was no joke, haven't looked in such things yet

ok I gotta sign out for now but feel free to pm or email me if you need anything, I ll take care of it later today

Setup development environment: @anuditverma, I think that's clear for now is it?

what will you use for it?

Well, that is the next task: Get acquainted with AXIOM beta, since my task doesn't require hardware much, so I would be using virtualisation tech and control daemon, currently Andrej is working on it, so I hope I will be getting my hands on with AXIOM development environment during this period.

yes, that is correct

Regarding dev env: I think we should include questions about using flatbufs or a C lib (what we were discussing right now)

Thx, added to issue

good question, this should be investigated first, but the prototype is focussed on C lib, although there is no lib at the moment, juast a small executable

if Anudit can replicate the current client functionality and communicate to the main app, which will become daemon later, then we would have some data to compate

*compare

yes, it's just not daemonized yet, which is a bigger task for later

nothings special is required

*nothing

Anudit can use it to brush up his Go skills, according to his proposal

If I can go with flatbuff https://google.github.io/flatbuffers/flatbuffers_guide_tutorial.html it's well documented and I believe I can catch up pretty quick

sounds great, does it?

Anudit: can you achieve replicating https://github.com/apertus-open-source-cinema/beta-software/blob/master/axiom_beta_control_daemon/API/ClientExample.cpp in go in may?

client.h

noted

okay

@anuditverma: Please take a look at unit testing in go and use it from the very beginning

ok ok I will see

https://golang.org/pkg/testing/

yes, as we have a lot of work, especially when it comes to the different buffers, interfaces etc. on camera

got it :)

and then Bertl will tell us his opinion and we have to rework it from the beginning :D

*unit testing

what's the meaning of life?

42

:D

i see you guys know the good stuff

we should meet in the middle of the week

Great

wednesday is good

Could we meet a bit earlier?

but Anudit can contact me at any time if there are questions

Ok great @BAndiT1983

Great!

Cool

also my e-mail address was already included in the mails from se6astian i suppose

Alright, meeting closed, see you next Wednesday

e-mail?

sent it

off to bed now ... have a good one everyone!