#apertus IRC Channel Logs

morning folks!

(From Twitter)

but if you assume that 4k (wide format) is 3840x2160 then yes, you can capture slightly more than that

hello everyone !

quick question : do we have a list of wifi dongle we already know that work with the beta ?

will give you a list of wifi drivers currently compiled in

e.g. modinfo rtl8192de

basically realtek variants rtl81* have been tested/used so far

another question : I'm making the alpha-like plexiglass case and I was thinking to make (lots of small) holes just behind the fan ("rear" part of the case then). Should I consider making other holes on other sides (there will be holes for power, ethernet, hdmi anyway)?

so you need to carefully consider where the air comes in and where it leaves the case

and I would make sure that there is near to nothing which keeps the air from flowing out there

if you simply put a few 'holes' at the back and have a gap between fan and case, the hot air will mostly circulate inside the case, which is not what you want :)

so more one big hole (the size of the fan) + something to make a tunnel from the exit of the fan to this hole

also measure the various temperatures on the camera and monitor them with and without case

a script for collecting all the temp sensor data would be nice btw

i.e. the resulting image will be 4096x3072

Thanks.

hopefully will do it this afternoon ! Of course, plenty of pictures !

that will only give you the zynq temp, there is a temp sensor on the power board as well and the sensor register 127 provides information as well

cmv_reg 127

around/above how much °C is temperature too high ?

and for a script, how much mesure per minute should I take ?

can you be more specific for each part of the camera ?

for the sensor, you want to keep that quite low, typically not more than a few degrees above room temperature

also, always keep in-take holes/slits at the bottom or at least bottom side, because of natural convection

might work, really depends on the placement

(in total, which is the inside area of the fan)

yep, but don't count the holes for plugs in full, they will be mostly obscured by connectors (I hope)

if you have too little intake, the fan gets slowed down, if you have to much, cooling will be ineffective

gotta go to join Nikos, be back online in one hour, hopefully making some holes !

new question : where would be the best place to write startup scripts (ex: ./set_gain.sh 2 ; ./gamma_conf.sh 0.3 ; and so on...) ?

kick.sh and halt.sh are normally executed on start up and shut down when the cmv12k service is enabled

Bertl, i suppose we need some mechanism which lets daemon execute scripts at startup, as REST gsoc falls into the same category of controls

of ArchLinux -> (05:53:20 PM) max_bxl_: 14:04:02> new question : where would be the best place to write startup scripts (ex: ./set_gain.sh 2 ; ./gamma_conf.sh 0.3 ; and so on...) ?

Hello everyone

hi Anudit

well, systemd is running on the Beta anyway, so systemd can trigger whatever setup necessary via the control daemon

we need just a small mechanism for that, but this can be elaborated while gsoc is ongoing

hi

hello __m__!

should we wait for se6astian?

I will check if he has time today

Sebastian won't be here today

with 1.8 it was reduced to 1mb, but i don't remember if optimized or not

Anudit, you can start

We will fix that asap, hopefully this week

ohh okay

When did you try to access the cam first?

(so that we know since when it's not accessible)

Ok cool

i can just forward it, as i'M sitting a little bit far away from vienna ;)

I have started with re writing https://github.com/apertus-open-source-cinema/beta-software/blob/master/axiom_beta_control_daemon/API/Client.h into GO lang

wrong = not working, not accessible or just very slow

have you committed some code? i need something to test with

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

Be so kind to stick to the git-flow scheme of commiting when pushing your work: http://nvie.com/posts/a-successful-git-branching-model/

I suggest you open a develop branch and work in feature branches

no, just a master branch with a readme atm

yes, we should merge only stale things into master

it's a good practice to work on "dev" branch and merge from time to time

And I think it would be great if we only merge proof checked code to master

just to have some sort of good maintenance

if it's possible to create a job which would build, test and then merge from dev to master, that would be perfect

I can do it end of may

ok thanks

*continuous

Committed code will be built automatically and build/test results will be posted on irc/github/,...

but dev to master only manually if possible

@anuditverma, camera should work, please try to connect

@BAndiT1983 I can push some code this weekend, I have just started

alright, as end of may is approaching we should hurry a bit, but the client is not complex at the moment, i think we could complete it this weekend, so it resembles C/C++ one

@anuditverma, great, so you will push this weekend to develop?

i've added a branch "develop", just clone it with your git client and then you can add code

don't worry if the code is not finished

anuditverma and Betl

Do you have any open questions atm @anuditverma?

anuditverma: have you succeeded in starting the daemon? this would help you to test your client, no witchcraft is required as it's an ordinary executable at the moment

great

Alright

May 24, 4pm UTC?

I can come for the meeting, my exam will be over by the day, I can join in the evening.

yes, i have time

Great, see you all next week 4pm UTC

bye