#apertus IRC Channel Logs

good day

good morning!

hi maxime!

fine !

great

hopefully we'll resume IRL meetings soon !

regarding the raw2dng conversion of your timelapse clip is everything clear now with the darkframe?

yep !

<se6ast1an> regarding the raw2dng conversion of your timelapse clip is everything clear now with the darkframe?

hi Sebastian

The re are change in the monitoring, but I guet weird stuff whenn "axiom-start"

sorry, occupied for a bit with a videoconference

let me know if you have any questions or need any support

is it normal to have this kind of results : https://pastebin.com/xJMM0k0b

?

ok, but it goes on and on forever

should I wait a bit more ?

yes

on the PC it takes ages too, but I'll give it another try then

which takes more time

the log says you also do row noise compensation "Row noise from black columns..."

ok

and make sure to snap the picture with -b enable black columns

maybe it tries to use black coloumns which are not there

ok

yes

perfect

yes

what DCNU stands for ?

thx

https://wiki.apertus.org/index.php/Raw2dng

--rnfilter=1 : FIR filter for row noise correction from black columns

and per-row median differences in green channels

--fixrn : Fix row noise by image filtering (slow, guesswork)

--fixrnt : Temporal row noise fix (use with static backgrounds; recommended)

I would suggest trying some/all of those and saving different resulting DNGs

how do you specify output in raw2dng ?

cat input.raw12 | raw2dng output.dng [options]

ie. cat input.raw12 | raw2dng output.dng --rnfilter=1 --fixrn --fixrnt

is it possible that "cat ..." doesn't pass metadata on ?

I got this ... https://pastebin.com/sR1iEv9g

indeed seems to be processed differently

max_bxl: I would recommend to use the first method for now and just rename the output dng afterwards

created task: https://lab.apertus.org/T1201

the --rnfilter=2 option seems better for our current setup

showing a side by side comparison of the different compensations would actually be a great addition to the wiki

off for lunch

will do with a color chart maybe

doesnt ned to be a color chat

I even think that a real life image is more interesting

ok will do then !

https://wiki.apertus.org/index.php/Raw2dng

thanks

you can zip dngs and upload to wiki as well

what does the dark frame calibration do ? (in order to add this to the wiki, as introduction of the section https://wiki.apertus.org/index.php/Factory_Calibration_(firmware_2.0)#Step_3:_Dark_frame_calibration )

could be a problem

12,8Mo zipped, 13,8Mo tar.gz

ah, right then files.apertus.org is probably a good place

yes, will do!

yes

https://www.apertus.org/magic-lantern-getting-to-grips-with-axiom-beta-image-sensor-article-feb-2016

thats the long answer

off for lunch

morning folks!

off for now ... bbl

regarding the AXIOM Remote GUI, I would like to discuss a feature I have in mind: I want to add a switch/option that allows the user to choose between setting parameters while the value is being changed or only after the selection has been completed

for example on a DSLR or broadcast/prosumer camera you expect to see a change in exposure time or aperture immediately, while turning a knob basically

so I would indeed like to add a button to each parametermenu where you can switch between LIVE/POST as you call it

the question is if the term "POST" is self expalantory

and if this choice should be saved with each parameter individually

in the end this has a lot of potential to confuse people

I guess I will also put these into a lab task

yes technically this should be easy to solve

https://lab.apertus.org/T1202

hi metal_dent[m], very good! had any problems?

nice!

it shouldn't really matter, as we want the data, also it's auto-generated, so don't worry

it can be solved rather easy with some tools, e.g. clang-format or similar, but focus on functionality first, can incorporate formatting when CircleCI is building

oh, Bertl is there, if you have 1 minute then i would like to know rather important info regarding the path for the PCB probe

have posted 2 images of the paths -> https://lab.apertus.org/T1199

makefile -> https://github.com/MetalDent/AXIOM-Remote/blob/dev/Firmware/Media/Icons/Makefile

BAndiT1983: can you use a script (or other way) to simply sum up the path lengths as metric?

can do, as i know the coordinates exaclty

metal_dent[m]: looks good!

alright then i'll sleep now! nn!

Bertl_oO: regarding the lengths, currently it's only between the element positions, but i suppose that the element BETA is in the center or so, it contains the connector pads

maybe i will just calculate all pad paths, then sort like now plus a threshold for position, as you will precalculate the paths, then i could add some command line threshold values for path "smoothing"

ok, will implement that, just simple trigonometry

i know, that's exactly the first thing i've stumbled when started to search for a solution

maybe there is a module in python for this

let me reflect a bit on that problem, it's solvable, will use pad position and element placement as factor and weighting or so

there is always a module for python ;) https://pypi.org/project/tsp/

well, you'll see :)

*later

it currently breaks the build though...

I did, thats how I created them

UI/Screens/MainMenu.h:54:64: error: no matching function for call to 'NumericMenuItem::SetHandler(void (MainMenu::*)(void*))'

it has to be static in the class

ah!

my implementation is not that polished yet though

no problem

pushed fix that should fix the build again

handler works, off to tv evening

off to bed

nn

register dumps from the camlink: https://paste.niemo.de/higaxonabi.makefile

good night everyone!

anuejn: ah, nice, tx

did not look at them yet