#apertus IRC Channel Logs

morning folks!

good day!

hey everyone i'm bit to early :-)

indeed :)

yep

i would be happy too

actually I see myself more as meeting organizer, I dont have much to add to the discussion topic itself

I just wanted to get you two together to make sure we know the next steps and that everyone knows where we are/what the other is doing

frontend i'm still not in a final version but some parts are working and other functions can be added on a later stage.

right

started to adjust some things yesterday, mostly to reduce cmake scripts complexity, instead git submodules were introduced

but all in all, basic comm worked rather fine and i could get right messages from the UI, which were also returned by the WS server, after processing through daemon

where i can help ?

is there also a daemon where i can test localy or is it the VM?

yes the first communication is surly not a small task

ahh okey will try that end of the week.

just check IRC logs for this channel on irc.apertus.org, to see if there was status update from me

let me check

this adjustments are for UI and daemon comm, as i've extended the packet a bit, also for the UI connectiom

will get to you on that stuff soon, but first command we should try is definitely gain -> DaemonCLI image_sensor set_gain 3

so set_gain is the current goal

okey at the moment the json file is still there i can add that in the json file

do we have some UI related questions or problems?

in my view is the most important thing that you have a interface where you can work with.

whats also i'm not sure if we need get / set i would love to have one sync command so i don't have to request all commands manualy.

json file makes the UI / at the moment just a pull down list or in the search bar

i will probably adjust packet structur a bit and intoduce command attribute, e.g. "module": "image_sensor", "command" : "get", "parameter": "gain"

it would simplify the processing a bit and allow to send "sync" as command, which retrieves handshake response again or maybe also just a simplified version of it, e.g. without ranges etc.

let us do this steps for now, before we store UI definitions in camera

store the UI is low priority. there are not many users yet :-)

job or leisure?

leisure.... no job

that's a nice tour you make there

yes i think my best decision since decades, just now in taipei and i like it very much.

i just now change some part in json file and test if that works and i will update in next 10min.

another thing, which will be reactivated and adjusted, are unit tests, so you can check the format of packets and also if it works

okey sounds good.

*useful

as a note the searchbar has a tab function so when you press: "g" and gain is top just use TAB and you see all values enter value and ENTER

it has some bugs but this works :-)

ongoing development, so no problem there

https://github.com/apertus-open-source-cinema/axiom-beta-firmware/blob/master/software/scripts/set_gain.sh

ohh i used digital gain and not analog gain, is the data in the AXIOM Beta Control Parameter List correct? i also can add digtal Gain.

*your

my tests focussed on that script and it's functionality, replicated them in the daemon, to have something real for tests

heading off now

in the json there is also a command parameter you can add there set_gain if you use it that way.

do you need some more? otherwise i would end it.... my bed is calling :-)

nothing important at the moment, you were helpful already, have a good night

https://vimeo.com/299272995

off for today