#apertus IRC Channel Logs

Hi, Bertl, I have a question regarding RAW12 format

?

A hex dump of first few bytes looks as follows: 08 00 77 08 50 77 07 60 6D 07 00 75 0D 90

However, both big endian and little endia do not have lsb 0 in any pattern I can see (16 bytes at once)

but note that we also have a raw16 format which uses 16bit per sensel

ping Bertl hi!

hey

Bertl, RAW12 are tightly packed, so one has to extract them to 16bit first

2x12 bit

why's that?

or you convert them at once to 8bit, but with less precision

which data type? ;)

didn't say that

hey supragya! check the IRC logs

Few questions: sensel packed...(could not understand)

in a stream of data bits, every 12 bits contain one sensel, no padding

the 12bit version leaves out the zero padding, yes

k

however, what exactly are these 2 channels? doesnot look like RGB (then it would be 3), is it input from 2 different lenses?

so the first line goes RGRGRGRG...

so am i right that [08 00 77] & [10101010 00000000] would give me debayered R?

thank you for the help, Bertl, I will ping you in if something else comes up. Can u point me to some related documents which I can refer to in the meanwhile, to get a better understanding

and of course the cmv_snap sources

https://github.com/apertus-open-source-cinema/beta-software/tree/master/software/cmv_tools

np

usuall RGGB, but you can also find it out by assigning manually

you can also look in OC, there is ProcessingTest which shows which methods are called for debayering, this ones are in OCcore

thank you Bandit.

however, what is OC?

:D

Bertl, had a question yesterday about orientation markers on PCBs, it's about automatic inspection

let's hear ...

tested template matching with opencv, python for now as javascript version was complicated to come by

what are the usage cases for automatic inspection? seen some scans of boards without parts and some gray stuff on the pads, other scans had same boards, but already with chips

I presume the main purpose will be to check proper orientation and correct soldering on the final PCB, but se6astian certainly knows more

okay?

by guidelines i mean, if all the parts have text near them, this would simplify the job to find right areas

not sure why you want to detect the text?

i've seen different ones, some boards have NE, SW etc.

detection is done by using a template, small part of the image in that case, as i suppose that we have always the same scanner for now

i suppose, that one task would be to find right orientation and to rotate the scan, but also to use homography possibly, as i can't tell if template matching would be sufficient

I think it should be doable to always scan them the 'right' way round

okay, then we can avoid this part for now, will implement something just to learn opencv better

which fiducials are there? as i said, seens different ones

what are the containers, which are green or orange, around PCBS?

(the fiducials)

alright, then i've looked at the right ones

excellent

not that it would be important, as i would try to create some masks, so we can cut background off, but maybe it would be easier after all

when Sebastian is well again, we can discuss more details, will create some methods beforehand, but in python for now, as it was easier to set up and didn't want to involve C++ as later i still plan to create a web interface if we pursuit this idea further