Current Server Time: 15:11 (Central Europe)

#apertus IRC Channel Logs

2017/05/12

Timezone: UTC


06:04
Rex0r
left the channel
07:09
Rex0r
joined the channel
07:55
se6astian|away
changed nick to: se6astian
07:56
se6astian
good day
08:34
Bertl_zZ
changed nick to: Bertl
08:34
Bertl
morning folks!
08:49
Rex0r
Greets.
09:08
davidak
joined the channel
09:58
niemand
joined the channel
09:58
niemand
left the channel
09:58
niemand
joined the channel
10:23
niemand
left the channel
10:24
niemand
joined the channel
10:24
niemand
left the channel
10:24
niemand
joined the channel
10:34
intracube_afk
changed nick to: intracube
10:46
davidak
left the channel
10:53
sebix
joined the channel
10:53
sebix
left the channel
10:53
sebix
joined the channel
10:56
RexO
joined the channel
10:56
Rex0r
left the channel
10:57
niemand
left the channel
11:01
davidak
joined the channel
11:34
sebix
left the channel
11:42
axiomhq
left the channel
11:42
axiomhq
joined the channel
11:52
sebastian_
joined the channel
12:39
davidak
left the channel
12:53
pusle
left the channel
12:56
davidak
joined the channel
12:57
pusle
joined the channel
13:00
davidak
left the channel
13:18
davidak
joined the channel
13:27
davidak
left the channel
13:29
sebastian_
left the channel
13:50
Bertl
off for a nap ... bbl
13:50
Bertl
changed nick to: Bertl_zZ
14:32
maltefiala
joined the channel
14:48
illwieckz
left the channel
14:51
illwieckz
joined the channel
14:56
davidak
joined the channel
15:11
Rex0r
joined the channel
15:24
davidak
left the channel
15:36
shsec
joined the channel
15:37
shsec
left the channel
15:37
maltefiala
left the channel
15:37
jucar
joined the channel
15:37
maltefiala
joined the channel
15:44
Bertl_zZ
changed nick to: Bertl
15:44
Bertl
back now ...
16:00
se6astian
changed nick to: se6astian|away
16:06
jucar
left the channel
16:07
BAndiT1983|away
changed nick to: BAndiT1983
16:11
dimon_
joined the channel
16:12
dimaursu16
left the channel
16:15
Bertl
off for dinner, bbs
16:15
Bertl
changed nick to: Bertl_oO
16:45
champika
joined the channel
16:53
RexO
left the channel
16:54
Rex0r
left the channel
16:54
Bertl_oO
changed nick to: Bertl
16:54
Bertl
back now ...
16:55
Rex0r
joined the channel
16:58
sebix
joined the channel
17:47
champika
left the channel
17:53
niemand
joined the channel
17:54
se6astian|away
changed nick to: se6astian
17:56
sebix
left the channel
17:57
anuditverma
joined the channel
17:57
se6astian
hi anuditverma
18:00
se6astian
whats your local time currently?
18:02
anuditverma
it is 10:32pm here
18:04
se6astian
right
18:05
se6astian
BAndiT1983: you here as well
18:05
BAndiT1983
yes
18:06
se6astian
great, maltefiala?
18:08
anuditverma
So today's meeting is on a different channel ?
18:08
champika
joined the channel
18:11
se6astian
if we discuss anything internal we can go to a private room
18:11
se6astian
but so far I think there is nothing confidential
18:11
anuditverma
okay
18:11
se6astian
well lets start without maltefiala, he might turn up soon
18:12
se6astian
did you try the remote beta access login?
18:12
Bertl
(please avoid Beta access details on the logged channel :)
18:13
se6astian
of course
18:13
se6astian
but all the credentials are exchanged over email already
18:13
anuditverma
@se6astian not yet, I will try it tonight
18:14
se6astian
great
18:14
anuditverma
@Bertl yes I know ;)
18:14
Bertl
tx, appreciated :)
18:15
se6astian
so about the API and the control daemon I was hoping malte and BAndiT1983 could discuss the plan a bout more in detail
18:16
se6astian
lets hope malte joins us soon
18:18
BAndiT1983
current progress can be found on github, haven't proceeded further as we didn't know which tasks would make it into finals
18:19
anuditverma
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 ?
18:20
se6astian
you can capture images over the commandline
18:20
se6astian
and pipe them into a file to ddownload/convert or analyse remotely
18:20
se6astian
live video feed is a bit more difficult
18:21
anuditverma
alright, got it
18:22
anuditverma
@BAndiT1983 thanks, I will follow the repo, I have the link
18:23
maltefiala
hej there
18:23
maltefiala
sry for being late
18:23
BAndiT1983
many things are still missing, but it can already distinguish between different settings, so we can implement different processors for each type
18:23
anuditverma
Hello @maltefiala
18:23
BAndiT1983
feedback channel is not there yet, but i read something about half-closing the socket for that
18:24
se6astian
note that the remote access beta currently has no lens attached (unless Bertl changed that 2 days ago)
18:24
se6astian
so while you can capture images I expect them to be all black
18:25
Champika_oO
joined the channel
18:26
BAndiT1983
i think that image capturing is less important currently, we have to get other things running, before real tests can be done
18:26
champika
left the channel
18:27
Champika_oO
left the channel
18:27
champika
joined the channel
18:28
maltefiala
Alright, so regarding the task
18:28
maltefiala
https://lab.apertus.org/T723
18:29
maltefiala
You sent us a suggestion for a timeline and I think it's good we should go for it
18:30
anuditverma
Well Yes, we can make some changes (if required) as we go but I want to stick to it right now
18:33
BAndiT1983
what will be used for REST?
18:33
maltefiala
What do you mean?
18:33
BAndiT1983
which language do you start with? as there were some on the list
18:34
se6astian
I ll create a github repo now for the task and give you access
18:34
maltefiala
We decided to use go as mentioned in T723
18:34
maltefiala
https://lab.apertus.org/T723
18:34
BAndiT1983
is it updated with the proposal list?
18:35
BAndiT1983
alright, then we need the connection between Go and client lib
18:35
anuditverma
according to my timeline , I would start with Go lang to build a basic client app
18:35
maltefiala
Yes, that is right
18:36
BAndiT1983
how long would it take to develop this app?
18:37
anuditverma
Though I have been still learning and brushing up my GO, a week or less would do
18:37
maltefiala
@anuditverma, could you link the timeline, is that ok for you
18:38
maltefiala
?
18:38
maltefiala
I suggest we stick to the timeline
18:38
anuditverma
@BAndiT1983 It's a week job on my timeline
18:39
BAndiT1983
i will also take a look how Go can be used with C/C++ bindings
18:40
anuditverma
@maltefiala my proposal : https://goo.gl/TXCYJY
18:41
maltefiala
@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?
18:41
maltefiala
@anuditverma: thx
18:41
BAndiT1983
socket is already there
18:41
se6astian
https://github.com/apertus-open-source-cinema/axiom-beta-rest-api created
18:41
BAndiT1983
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
18:42
se6astian
I invited you 3 with write access
18:42
BAndiT1983
thanks
18:42
se6astian
please check if it works
18:42
anuditverma
@se6astian Thanks
18:42
anuditverma
invite accepted
18:43
se6astian
renamed to https://github.com/apertus-open-source-cinema/axiom-beta-rest-interface
18:43
anuditverma
all looks good on my end
18:43
maltefiala
@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
18:44
maltefiala
Other services could access this socket
18:44
BAndiT1983
i use flatbuffers as they are really small
18:44
BAndiT1983
other advantage is that they support types
18:45
BAndiT1983
you can see it here -> https://github.com/apertus-open-source-cinema/beta-software/blob/master/axiom_beta_control_daemon/Schema/axiom_daemon.fbs
18:46
BAndiT1983
JSON requires a lot of data conversion, which is not good for performance
18:46
BAndiT1983
https://github.com/apertus-open-source-cinema/beta-software/blob/master/axiom_beta_control_daemon/API/ClientExample.cpp
18:46
maltefiala
@BAndiT1983, I think flatbuffers are great
18:46
BAndiT1983
this is how client is sending data at the moment
18:47
BAndiT1983
we can try to replicate client in Go, to see how it works out
18:48
maltefiala
Go has native support for flatbuffers as far as I know so no need for an extra lib if we can access the socket
18:48
maltefiala
http://google.github.io/flatbuffers/
18:49
BAndiT1983
but if we need another language, we have to reimplement the functionality
18:50
maltefiala
The go application is just a rest interface, the functionality of changing parameters will be in the daemon anyways so I don't think it is a problem
18:50
maltefiala
What do you think?
18:50
maltefiala
go app: Change param lens -> daemon changes param lens
18:50
maltefiala
*lense
18:50
BAndiT1983
just saying, that if python will come into play, then the client has to be implemented there
18:51
BAndiT1983
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
18:52
maltefiala
What functionality are you thinking of?
18:53
BAndiT1983
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
18:53
maltefiala
@anuditverma, flatbuffer lang support table: http://google.github.io/flatbuffers/flatbuffers_support.html
18:53
BAndiT1983
https://github.com/apertus-open-source-cinema/beta-software/blob/master/axiom_beta_control_daemon/API/Client.h
18:54
anuditverma
@maltefiala I am following...
18:54
maltefiala
I am ok with either options (C lib or just flatbuffers)
18:55
BAndiT1983
you could try to get the things done in Go, just want to show the possible obstacles
18:56
BAndiT1983
i will still continue to develop the C/C++ client, as i need some test platform
18:56
maltefiala
If @anuditverma utilises the C library, what is still missing on the C side?
18:56
maltefiala
Because @anuditverma s task is doing the go rest interface
18:57
anuditverma
I see Simple mutation and fuzz Testing missing on the table for C
18:57
BAndiT1983
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
18:57
anuditverma
left the channel
18:58
anuditverma
joined the channel
18:58
BAndiT1983
you don't need mutation, as the data is provided read only to daemon
18:58
BAndiT1983
don't know what fuzz is about? no pun intended
18:59
anuditverma
haha okay
18:59
BAndiT1983
it was no joke, haven't looked in such things yet
19:00
anuditverma
ok cool
19:01
se6astian
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
19:01
maltefiala
kk
19:02
se6astian
changed nick to: se6astian|away
19:02
maltefiala
Ok, so regarding the timeframe until May 30:
19:03
maltefiala
Setup development environment: @anuditverma, I think that's clear for now is it?
19:03
anuditverma
Yes :)
19:03
BAndiT1983
what will you use for it?
19:04
anuditverma
Right now I will access the beta and get myself familiar with parameter usage
19:05
maltefiala
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.
19:05
maltefiala
Last one until May 30: As per the Prerequisites of this project, I have been learning Go for a while now and have acquired basic skills to code in Go or build as App, also I want to brush up my Golang more in this phase and become ready when the actual coding begins in the Coding Period.
19:06
anuditverma
yes, that is correct
19:07
BAndiT1983
https://wiki.apertus.org/index.php/AXIOM_Beta/AXIOM_Beta_Software
19:07
maltefiala
Regarding dev env: I think we should include questions about using flatbufs or a C lib (what we were discussing right now)
19:07
BAndiT1983
there are many things about parameters and general usage, but camera is not important to me at the moment, comm between daemon and client is much more important
19:07
maltefiala
Thx, added to issue
19:08
maltefiala
Regarding com between daemon and client: How shall we do this now?
19:09
se6astian|away
changed nick to: se6astian
19:09
maltefiala
C lib or flatbufs and how can we ensure anuditverma can start first of june?
19:09
BAndiT1983
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
19:10
maltefiala
Should one of us create a mock for anudit or will you be able to code the c lib or the flatbuf part until end of may?
19:11
BAndiT1983
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
19:11
maltefiala
anuditverma, if you want / can help out here feel free to say so
19:11
BAndiT1983
*compare
19:11
maltefiala
Main app = control daemon?
19:11
BAndiT1983
yes, it's just not daemonized yet, which is a bigger task for later
19:12
BAndiT1983
i use linuxmint and start daemon app, then client app to see the results, also htop to see memory and CPU usage
19:12
BAndiT1983
nothings special is required
19:12
maltefiala
So first task in June could be replicating this functionality in go? https://github.com/apertus-open-source-cinema/beta-software/blob/master/axiom_beta_control_daemon/API/Client.h
19:12
BAndiT1983
*nothing
19:12
BAndiT1983
i would do it in may, so we can decide how to proceed
19:13
BAndiT1983
Anudit can use it to brush up his Go skills, according to his proposal
19:13
maltefiala
"i would do it in may, so we can decide how to proceed" @BAndiT1983, you will be able to finish the C lib in may?
19:14
anuditverma
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
19:14
maltefiala
Oh, ok, I understand
19:14
maltefiala
sounds great, does it?
19:15
BAndiT1983
don't think that it's always easy, FB has also its quirks, so sometimes you want to pull the hair as the data looks awkward
19:16
maltefiala
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?
19:16
anuditverma
Till end of May ? yes I can
19:16
BAndiT1983
client.h
19:17
maltefiala
Great. So that is part of #3 then
19:17
anuditverma
noted
19:17
BAndiT1983
clientexample is just a showcase for usage of the API
19:17
anuditverma
okay
19:18
maltefiala
Sure, I suggest to implement the example as well so we know it works
19:18
maltefiala
@anuditverma: Please take a look at unit testing in go and use it from the very beginning
19:19
anuditverma
@maltefiala This is what I meant when I said above we can modify the timeline as required
19:19
anuditverma
ok ok I will see
19:19
BAndiT1983
good idea, will also attach something to the C/C++ part
19:19
BAndiT1983
https://golang.org/pkg/testing/
19:20
maltefiala
@anuditverma: I think it is best to not alter the timeframe too much. Don't rush to the goal in may. It is better to get a good understanding of how go, unittesting and flatbuffers work
19:20
BAndiT1983
yes, as we have a lot of work, especially when it comes to the different buffers, interfaces etc. on camera
19:21
BAndiT1983
so it has to be done thoroughly
19:21
anuditverma
got it :)
19:21
maltefiala
Great
19:22
BAndiT1983
and then Bertl will tell us his opinion and we have to rework it from the beginning :D
19:22
maltefiala
Regarding unit questions I compiled a list of links in the original task description as well: https://lab.apertus.org/T723
19:22
maltefiala
*unit testing
19:23
maltefiala
Alright, any questions?
19:23
BAndiT1983
what's the meaning of life?
19:23
maltefiala
Oh yes, regarding meeting times, what times do you prefer? I suggest we meet once in a week
19:23
maltefiala
42
19:23
anuditverma
42
19:23
anuditverma
:D
19:23
maltefiala
:D
19:23
BAndiT1983
i see you guys know the good stuff
19:24
anuditverma
Do read http://www.anudit.in/2015-09-06-this-is-your-quest-for-space-exploration/ when free
19:24
BAndiT1983
we should meet in the middle of the week
19:24
maltefiala
And I would prefer not meeting on Friday
19:24
maltefiala
Great
19:24
maltefiala
What about Wednesday?
19:25
BAndiT1983
wednesday is good
19:25
anuditverma
I am comfortable with Wednesday
19:25
maltefiala
Could we meet a bit earlier?
19:25
maltefiala
Perhaps 16:00 UTC?
19:25
BAndiT1983
but Anudit can contact me at any time if there are questions
19:26
anuditverma
Yeah Sure
19:26
anuditverma
Ok great @BAndiT1983
19:26
BAndiT1983
time sounds ok
19:26
maltefiala
Great!
19:26
BAndiT1983
you can try it on IRC or through PM in lab
19:27
anuditverma
Cool
19:27
maltefiala
So we meet next Wednesday 16:00 UTC
19:27
BAndiT1983
also my e-mail address was already included in the mails from se6astian i suppose
19:27
maltefiala
Yes, I wrote a mail to all of you you should have each other's addresses
19:28
maltefiala
Alright, meeting closed, see you next Wednesday
19:28
BAndiT1983
ok
19:29
maltefiala
left the channel
19:29
anuditverma
@BAndiT1983 I checked, I guess it's not mentioned, could you please pm me
19:30
BAndiT1983
e-mail?
19:30
anuditverma
yes yes
19:30
BAndiT1983
sent it
19:31
anuditverma
Thanks, goodnight, see you all in the next meeting
19:32
anuditverma
left the channel
19:33
__m__
joined the channel
19:33
anuditverma
joined the channel
19:34
anuditverma
left the channel
20:03
Spirit532__
joined the channel
20:07
Spirit532_
left the channel
20:22
BAndiT1983
changed nick to: BAndiT1983|away
21:12
champika
left the channel
21:17
Bertl
off to bed now ... have a good one everyone!
21:17
Bertl
changed nick to: Bertl_zZ
21:48
se6astian
changed nick to: se6astian|away
22:32
niemand
left the channel