00:26 | Bertl | off to bed now ... have a good one everyone!
| |
00:26 | Bertl | changed nick to: Bertl_zZ
| |
01:23 | jucar | joined the channel | |
01:56 | jucar | left the channel | |
02:22 | slikdigit | joined the channel | |
03:59 | slikdigit | left the channel | |
04:18 | slikdigit | joined the channel | |
06:02 | slikdigit | left the channel | |
07:19 | Bertl_zZ | changed nick to: Bertl
| |
07:19 | Bertl | morning folks!
| |
09:14 | Rex0r | Is there the possibility of capturing the full sensor readout for larger than 4k video?
| |
09:15 | Rex0r | (From Twitter)
| |
09:18 | Bertl | the sensor is 4k i.e. 4096x3072 so there is nothing more to capture than that
| |
09:19 | Bertl | but if you assume that 4k (wide format) is 3840x2160 then yes, you can capture slightly more than that
| |
09:27 | max_bxl | joined the channel | |
09:27 | max_bxl | hello everyone !
| |
09:27 | Bertl | hey max_bxl!
| |
09:28 | max_bxl | quick question : do we have a list of wifi dongle we already know that work with the beta ?
| |
09:30 | Bertl | [root@beta ~]# find /lib/modules/`uname -r`/kernel/drivers/net/wireless/ -iname '*.ko*'
| |
09:30 | Bertl | will give you a list of wifi drivers currently compiled in
| |
09:31 | Bertl | you can then check each of them with 'modinfo <module>' what hardware it supports
| |
09:31 | Bertl | e.g. modinfo rtl8192de
| |
09:32 | max_bxl | great !
| |
09:32 | Bertl | basically realtek variants rtl81* have been tested/used so far
| |
09:34 | max_bxl | ok
| |
09:36 | max_bxl | 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)?
| |
09:38 | Bertl | well, in a closed case, it is all about the air flow
| |
09:38 | Bertl | so you need to carefully consider where the air comes in and where it leaves the case
| |
09:39 | Bertl | obviously the main point to leave the case is where the fan is
| |
09:39 | Bertl | and I would make sure that there is near to nothing which keeps the air from flowing out there
| |
09:40 | Bertl | i.e. best make some kind of wind tunnel which directly connects to the fan top
| |
09:40 | Bertl | 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 :)
| |
09:41 | max_bxl | ok
| |
09:42 | max_bxl | so more one big hole (the size of the fan) + something to make a tunnel from the exit of the fan to this hole
| |
09:48 | Bertl | yeah, something like that
| |
09:49 | Bertl | also measure the various temperatures on the camera and monitor them with and without case
| |
09:50 | Rex0r | And capturing the full sensor output is just a case of running some commands yeah?
| |
09:50 | Bertl | a script for collecting all the temp sensor data would be nice btw
| |
09:50 | Bertl | Rex0r: cmv_snap does capture the full sensor data
| |
09:50 | Bertl | i.e. the resulting image will be 4096x3072
| |
09:51 | Rex0r | When do you reckon you'll have done this by max_bxl? Will you take plenty of photos of the build process?
| |
09:51 | Rex0r | Thanks.
| |
09:56 | intracube_afk | changed nick to: intracube
| |
09:58 | max_bxl | hopefully will do it this afternoon ! Of course, plenty of pictures !
| |
10:00 | max_bxl | for the temperature, I guess I should use ./zynq_info.sh ? Any other command to monitor other parts ?
| |
10:01 | Bertl | 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
| |
10:02 | Bertl | cat /sys/class/hwmon/hwmon0/temp[0-9]_input
| |
10:02 | Bertl | cmv_reg 127
| |
10:03 | max_bxl | ok
| |
10:04 | max_bxl | around/above how much °C is temperature too high ?
| |
10:04 | Bertl | that really depends on the part of the camera
| |
10:05 | max_bxl | and for a script, how much mesure per minute should I take ?
| |
10:05 | Bertl | for the zynq, it will work relatively fine up to 90°C, although that is a little high for normal use
| |
10:05 | max_bxl | can you be more specific for each part of the camera ?
| |
10:05 | max_bxl | sorry too impatient !
| |
10:06 | Bertl | for the sensor, you want to keep that quite low, typically not more than a few degrees above room temperature
| |
10:06 | Bertl | (so adding slits or holes near the sensor for air intake is a good idea, but don't over-do it :)
| |
10:07 | Bertl | also, always keep in-take holes/slits at the bottom or at least bottom side, because of natural convection
| |
10:08 | max_bxl | ok ! two thin slits (3x20mm) on the front side for example ?
| |
10:09 | Bertl | might work, really depends on the placement
| |
10:10 | Bertl | as a rule of the thumb, you want to have about 1.5-2x the area you get for the exhaust
| |
10:10 | Bertl | (in total, which is the inside area of the fan)
| |
10:11 | max_bxl | "1.5-2x the area you get for the exhaust" for all the air intakes I'll make (also with the ethernet holes and so on), right ?
| |
10:13 | Bertl | yep, but don't count the holes for plugs in full, they will be mostly obscured by connectors (I hope)
| |
10:13 | max_bxl | sure ! I thought so ^^
| |
10:14 | Bertl | if you have too little intake, the fan gets slowed down, if you have to much, cooling will be ineffective
| |
10:18 | max_bxl | noted !
| |
10:18 | max_bxl | gotta go to join Nikos, be back online in one hour, hopefully making some holes !
| |
10:19 | Bertl | cya
| |
10:32 | max_bxl | left the channel | |
12:38 | intracube | left the channel | |
13:06 | intracube | joined the channel | |
13:16 | max_bxl | joined the channel | |
13:37 | jucar | joined the channel | |
13:39 | max_bxl | left the channel | |
14:02 | max_bxl_ | joined the channel | |
14:02 | max_bxl_ | hello again !
| |
14:04 | max_bxl_ | 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...) ?
| |
14:08 | slikdigit | joined the channel | |
14:31 | jucar | left the channel | |
15:02 | Bertl | depends on when you want them to run :)
| |
15:02 | Bertl | kick.sh and halt.sh are normally executed on start up and shut down when the cmv12k service is enabled
| |
15:14 | anuditverma | joined the channel | |
15:34 | max_bxl_ | left the channel | |
15:53 | BAndiT1983|away | changed nick to: BAndiT1983
| |
15:54 | BAndiT1983 | Bertl, i suppose we need some mechanism which lets daemon execute scripts at startup, as REST gsoc falls into the same category of controls
| |
15:55 | Bertl | at what startup?
| |
15:56 | BAndiT1983 | 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...) ?
| |
15:56 | BAndiT1983 | if we have a daemon, then the scripts can be reworked and also reduced
| |
15:56 | anuditverma | Hello everyone
| |
15:57 | BAndiT1983 | further, some simple script parser for settings is required, but it's not a big deal
| |
15:57 | BAndiT1983 | hi Anudit
| |
15:57 | BAndiT1983 | as replacement for .sh ones
| |
15:59 | Bertl | well, systemd is running on the Beta anyway, so systemd can trigger whatever setup necessary via the control daemon
| |
15:59 | BAndiT1983 | that's what i've meant
| |
15:59 | BAndiT1983 | we need just a small mechanism for that, but this can be elaborated while gsoc is ongoing
| |
16:02 | __m__ | Hello
| |
16:02 | BAndiT1983 | hi
| |
16:02 | anuditverma | I tried ssh -ing into AXIOM beta setup, it seems the response time on it is very long, may be because of remote access I guess, or is it normal ?
| |
16:06 | Bertl | hello __m__!
| |
16:06 | __m__ | Hej!
| |
16:08 | BAndiT1983 | should we wait for se6astian?
| |
16:09 | __m__ | Yes, let's wait
| |
16:10 | __m__ | I will check if he has time today
| |
16:11 | BAndiT1983 | by the way, i've tried a bit golang, it was scary how big the compiled executable of "hello world!" was
| |
16:11 | __m__ | Sebastian won't be here today
| |
16:11 | BAndiT1983 | golang 1.6 -> 2.3mb without optimization, with 1.6
| |
16:11 | BAndiT1983 | with 1.8 it was reduced to 1mb, but i don't remember if optimized or not
| |
16:12 | BAndiT1983 | then we should do a quick meeting
| |
16:12 | BAndiT1983 | Anudit, you can start
| |
16:13 | __m__ | The cam seems to be offline atm
| |
16:13 | __m__ | We will fix that asap, hopefully this week
| |
16:13 | anuditverma | So I tried accessing the beta, it seems un responsive
| |
16:13 | anuditverma | ohh okay
| |
16:14 | __m__ | When did you try to access the cam?
| |
16:14 | __m__ | When did you try to access the cam first?
| |
16:16 | anuditverma | It was Saturday I think
| |
16:16 | __m__ | (so that we know since when it's not accessible)
| |
16:16 | __m__ | Alright, next time, please mail me or PM Sebastian/Bandit if something like this occurs so we can get rid of stopping tasks right away
| |
16:17 | anuditverma | Ok cool
| |
16:17 | __m__ | Alright, so, what's the status of your work?
| |
16:18 | BAndiT1983 | i can just forward it, as i'M sitting a little bit far away from vienna ;)
| |
16:18 | __m__ | Oh yeah, that's right, sorry. So please @anuditverma, mail me or PM sebastian if something with the cam is wrong
| |
16:19 | anuditverma | 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
| |
16:19 | anuditverma | well it's just a start
| |
16:19 | __m__ | wrong = not working, not accessible or just very slow
| |
16:19 | anuditverma | @__m__ alright I will do it surely
| |
16:19 | BAndiT1983 | have you committed some code? i need something to test with
| |
16:19 | __m__ | Could you periodically push your work to the repo?
| |
16:19 | __m__ | https://github.com/apertus-open-source-cinema/axiom-beta-rest-interface
| |
16:20 | BAndiT1983 | wanted to write the access in go, but remembered that you are on the task, so i stopped further investigation for now
| |
16:20 | __m__ | 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/
| |
16:20 | anuditverma | well not yet
| |
16:21 | aombk | left the channel | |
16:21 | BAndiT1983 | is there a "dev" branch yet?
| |
16:22 | __m__ | I suggest you open a develop branch and work in feature branches
| |
16:22 | anuditverma | So I keep a separate branch for my commits ?
| |
16:22 | __m__ | no, just a master branch with a readme atm
| |
16:22 | anuditverma | okay got it
| |
16:22 | BAndiT1983 | yes, we should merge only stale things into master
| |
16:22 | BAndiT1983 | *stable
| |
16:22 | BAndiT1983 | it's a good practice to work on "dev" branch and merge from time to time
| |
16:23 | __m__ | I would suggest to only work in feature branches and merge the develop when the feature is donw
| |
16:23 | aombk | joined the channel | |
16:23 | BAndiT1983 | if there are some totally different tests, then one can temporarily create additional branches, which should be removed later, feature-based development
| |
16:23 | __m__ | And I think it would be great if we only merge proof checked code to master
| |
16:24 | BAndiT1983 | __m__: we should involve CI early enough
| |
16:24 | BAndiT1983 | just to have some sort of good maintenance
| |
16:25 | __m__ | @BAndiT1983, yes, you are right, we should do that. I suggest we do this End of May, when at least some code is in the repo
| |
16:25 | BAndiT1983 | if it's possible to create a job which would build, test and then merge from dev to master, that would be perfect
| |
16:25 | anuditverma | Sorry, what's CI ?
| |
16:25 | __m__ | I can do it end of may
| |
16:25 | __m__ | Continous integration
| |
16:25 | anuditverma | ok thanks
| |
16:25 | BAndiT1983 | i mean a separate job, which is executed manually, so we control what is supplied to master
| |
16:25 | __m__ | *continuous
| |
16:26 | __m__ | https://travis-ci.org/
| |
16:26 | __m__ | Committed code will be built automatically and build/test results will be posted on irc/github/,...
| |
16:26 | BAndiT1983 | so, the feature branches should be merged into "dev", afterwards "dev" to "master" from time to time
| |
16:27 | BAndiT1983 | but dev to master only manually if possible
| |
16:28 | BAndiT1983 | Anudit, when do you think some code is there? i could help you to finish the basic implementation, as i really need some base to see what is still missing from the daemon
| |
16:29 | __m__ | @anuditverma, camera should work, please try to connect
| |
16:30 | BAndiT1983 | at some point in time i would also need such access, but it's not mandatory currently
| |
16:30 | anuditverma | @BAndiT1983 I can push some code this weekend, I have just started
| |
16:31 | anuditverma | @__m__ ok trying
| |
16:31 | BAndiT1983 | 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
| |
16:32 | anuditverma | okay I will try to finish it fast
| |
16:32 | __m__ | @anuditverma, great, so you will push this weekend to develop?
| |
16:33 | anuditverma | yes, the Go code for the client
| |
16:34 | BAndiT1983 | i've added a branch "develop", just clone it with your git client and then you can add code
| |
16:35 | anuditverma | thanks
| |
16:35 | BAndiT1983 | don't worry if the code is not finished
| |
16:36 | __m__ | Alright, so, we meet again next Wednesday 4pm UTC?
| |
16:37 | __m__ | anuditverma and Betl
| |
16:37 | __m__ | anuditverma and Bertl are talking about how to access the camera atm in private, so I guess that's settled
| |
16:38 | __m__ | Do you have any open questions atm @anuditverma?
| |
16:38 | aombk | left the channel | |
16:41 | BAndiT1983 | 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
| |
16:42 | anuditverma | The remote setup is working fine :) I am testing it bit further with help from Bertl
| |
16:44 | __m__ | great
| |
16:44 | anuditverma | @__m__ I think I am sorted for now, will ping if I need help for anything and yes remote testing is still in process
| |
16:46 | __m__ | Alright
| |
16:47 | __m__ | So, next meeting in one week ok for everyone?
| |
16:47 | __m__ | May 24, 4pm UTC?
| |
16:50 | Bertl | it's very likely that I'm around, although I'm not really required I guess :)
| |
16:53 | anuditverma | I can come for the meeting, my exam will be over by the day, I can join in the evening.
| |
17:06 | __m__ | @BAndiT1983, do you have time?
| |
17:08 | BAndiT1983 | yes, i have time
| |
17:09 | BAndiT1983 | sorry, was not here for a moment
| |
17:13 | __m__ | Great, see you all next week 4pm UTC
| |
17:13 | __m__ | Have a nice day
| |
17:15 | Rex0r | left the channel | |
17:15 | Bertl | you too!
| |
17:15 | BAndiT1983 | bye
| |
17:59 | Rex0r | joined the channel | |
18:11 | anuditverma | left the channel | |
18:11 | maxfuh | joined the channel | |
18:14 | max_bxl | joined the channel | |
19:12 | RexOrCine | joined the channel | |
19:26 | se6astian|away | changed nick to: se6astian
| |
19:26 | Bertl | off for a nap ... bbl
| |
19:26 | Bertl | changed nick to: Bertl_zZ
| |
19:43 | max_bxl | left the channel | |
19:43 | maxfuh | left the channel | |
19:45 | champika | joined the channel | |
19:53 | champika | left the channel | |
20:14 | se6astian | changed nick to: se6astian|away
| |
20:15 | se6astian|away | changed nick to: se6astian
| |
20:15 | se6astian | changed nick to: se6astian|away
| |
20:53 | aombk | joined the channel | |
20:58 | Rex0r | left the channel | |
21:17 | BAndiT1983 | changed nick to: BAndiT1983|away
| |
22:32 | Rex0r | joined the channel | |
23:13 | dimaursu16 | left the channel | |
23:37 | intracube | changed nick to: intracube_afk
|