#apertus IRC Channel Logs

who is here?

great, Dest123 would you like to share progress and start the reporting right away?

yeah sure

wb!

thx :) Bertl

I started creating multiple configurations of the channels and I plan to test them and see if I can pick up anything

I'm sending a constant pattern, supposed to be the test pattern, but somehow the pattern isn't easy for me to observe

the data is messed up somehow

that's it for me :)

Just the ones I sent you.

thanks!

sure a bit

xD

This now gained the additional ability to to a additional pass right before the next higher "SubpassWidget" is encountered, which makes it possible to do a (very inefficient) backdrop blur

looks cool

thats it from me this week

many thanks vup!

(oh I also have been thinking a lot about order independent transparency and how we could use it to make the rendering of these effects a lot more efficient, so if anybody has experience in this area I would be very interested to talk about that)

also vup and me discussed some changes for axiom-recorder to be able to express the required frame-merging in our pipeline descriptions

many thanks, please don't forget to update your wiki project entry

there are no links to code or blog post yet

yes please :)

so from now on project news again on https://mastodon.social/@apertus

https://www.apertus.org/google-summer-of-code-wrap-2021-article-september-2021

today me and manfred visited the technical university institute of manufacturing technology

a contact established through a past factoryhub manager

so definitely lots of potential opportunities for collaboration in the future

https://www.ffg.at/ausschreibungen/InnovationsscheckmitSelbstbehalt

where the grant covers 80% of the cost

beside the usual huge and small CNC machines they also have an electron microscope or high power CT machine to "look through" metal parts

hello yasmin! glad that you could make it!

Hello :D

and small tools and scripts to convert or analyze recordings

today I started with darkframe creation and compensation

whats happening now is mostly convenience with recording and file handling

darkframe, gainframe, etc.

everything is currently designed for the cmv_snap full frames so some changes and evaluations here and there are reqired

well the raw2dng tool has a --check-darkframe parameter

no darkframe:

Black refcol: ignored

Pixel noise : 6.15

Col noise : 2.83 (46.0%)

- even rows : 2.88 (46.8%)

Dark frame : darkframe-x1.pgm

Average : 8.55

Row noise : 2.30 (47.7%)

- odd rows : 0.15 (3.1%)

the missing dark current is still an issue I think as corrected images are noticeably darker

what I'd like to know is the variance of the dark frames, i.e. how much each dark frame deviates from the average

not sure the current codebase can output that...

okay, just keep the 'raw dark frames' around

sure

Bertl please finish us!

i have downloaded Vivado, and prepared resources for VHDL as i usually write verilog

and by thursday i will finish installation of Vivado, and the simple project in VHDL

Yes :D

Thank you ^_^

and she will be working on FPGA stuff, which we still need to define ;)

great!

no

so last week I spent most of the time on improving the raw mode and testing/verifying various aspects

this simplifies the reassembly of A and B frames into raw data as it is basic interleaving

we also added the raw markers, which are basically a special overlay mode which allows us to place framecounter and read/write buffer information inside the HDMI output

the next steps are to investigate how much data we can actually fit in a default 1080p60 frame and how much we can increase the clock rate

that's it from my side for this week

anyone else who wants to share/report?

Thank you :)

thanks for moderating!