Fiducial Mark Finding with the ESS
Getting Started v.53
Changes
from
the recommended version are written in red.
| 53 |
2008-02-12 |
zip |
zip |
zip |
Development:
- Computer freeze during monitor creation bug fixed
- migration to Visual
Studio 2005 SP1
- use Parametric Line Fit to fix bug in vertical strip fit. |
Installation:
- download the binary and the configuration of FlexMapX. The dll must
be registered and the configuration must merged into Widnows registry
(the same as any SySal2000 module).
-
if MS Visual Studio 2005 Service
Pack 1
is not installed, you need the runtime components
of libraries.
Download the "Visual C++ 2005 SP1 redistributable Package (x86)" from
the microsoft web site and install it in your workstation.
- use good mechanical references (alignment between references and
motion axes better than 0.5 mm over 10 cm)
- put the emulsion (and the mechanical references) with the lateral
marks outside the vacuum channel as shown
here.
- as xy reference it is possible to use the up-left corner (max X , min
Y) which (if the emulsion is placed as shown
here)is closest to the first
mark and is also the reference corner for
the BAM. Open the Default Machine of the FlexStage module and ADD a XY
Reference named "
XYReferenceLeftUp"
.
Map string:
-
a MARK is
the
POINT given by the intersection between two closest-to-the-corner
X-Ray lines. see the
"clone problem" below.
- load the map string exactly as
spot-like optical marks and change the keyword
"mapext" with "mapX", example:
mapX: 1029351 1 0 0; 2 0 0
125100 99800; 1 121675 2399 121675 2399 1 1 2; 2 121388 97203 121388
97203 1 1 2
or
mapX:
1029351
1 0 0; 2 0 0 125100 99800; 1 121675 2399
121675 2399 1 2; 2 121388 97203 121388 97203 1 2
This
revision integrates the spot-like mark searching. If you
send a string
starting with "mapext" the system will start a search for spot-like
mark set, as FlexMap3.dll, example: mapext: 1029351 1 0
0; 4 0 0 125100 99800; 1 9900 9899 9900 9899 1 1 2; 2 115208 10132
115208 10132 1 1 2; 3 115089 90507 115089 90507 1 1 2; 4 9844 90250
9844 90250 1 1 2
The map
load from a *.map
file is not implemented: only string is enabled.
Note: this revision does not check the consistency of the string (i.e. plate.min.X
< mark.position.X < plate.max.X ).
Configuration:
The
configuration integrates spot and lateral mark finding.
(click
here to see where FlexMap3
parameters are
now)
Lateral Mark
parameter
optimization was not done yet.
For a detailed
documentation
see here.[TO BE DONE]
Bug Report:
Bug in Spot Mark Finding.
WARNINGS:
Change in the strip
segments
strategy (see here)
The "clone"
problem:
The
presence of a duplicated x-strip 1 mm far from the reference one
("clone") caused
some failures during tests. See the mark position in the
picture.
Automatic
clone check:
after the first segment of a vertical strip is found, the system will
search for the clone vertical strip at DX= +1000 and DX=-1000. If
another strip is found, the closest-to-the-edge is
taken.
If you suppose to have acquired the wrong one, look
at log files to verify the mark position [ex:
flexmap_summary.log gives the summary of all stage coordinates
position.
They should be within a few 100 microns for one brick set even if
the emulsion plate is different. If a mark is 1 mm far along X
is the
wrong one].
Log Files:
This revision produces (many) log files which can be read with
notepad (or any log file viewer as BareTail):
c:\acq\VMarkFinder.log
<-- the logger of the current mark
finding routine
c:\acq\flexmap_summary.log <--
mark stage
position *append file*
Manual Set:
If the system is not able to find the mark you can SET the mark
manually: the mark is set as not searched and the system will try to
scan
again the mark using your position as starting point. You can also flag
the mark as FOUND without rescanning by clicking on "set found" after
the manual set.
Scanning
Infrastructure:
(v2.1 and v2.2 up to 2008-01-29)
The DB and the infrastructure are not updated to use
different mark
patterns for the same plate.
Hence, load the 2 lateral marks exactly as the spot case
and remember to flag ForceLateralMarkFinding
in the FlexMapX configuration (!) .
(v2.2 flag:290108
date:2008-01-29 and more)
Detailed
support
for multiple mark sets (Optical, X-Ray Lateral, CS X-Ray).
If
you want to test this edition, be aware that DB upgrade is needed for
the new MARKSET fields that documents the set of marks used.
The
plate-to-plate intercalibration with Lateral Marks are very close to
the identity transformation, so it is supposed that you want
to
disable intercalibration during driven scanning. To disable the
intercalibration during driven scanning, put the
intercalibrationID equal to the predictionID or to the
AreaScanConfigId:
in the scan back configuration put
<IntercalibrationConfigId> =
</PredictionId>
in the total scan configuration put
<IntercalibrationConfigId> =
</AreaScanConfigId>
Contact people:
Here, there are people of the Bologna Scanning Lab who have used the
module and (maybe) can give some help.
- Gabriele Sirri, +39 051 20 95228 /
95095
(LAB), sirri [at] bo.infn.it
- Michele Pozzato, +39 051 20 95230 / 95095 (LAB), pozzato
[at] bo.infn.it
Feedback and any kind of contribution are
welcome.
author: G. Sirri
back to scanning
