|
Size: 812
Comment:
|
Size: 3084
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| Describe NFT-1-setup here. | == Parameter File == |
| Line 3: | Line 3: |
| == CSV File == | |
| Line 5: | Line 4: |
| For each delivery, make a control file extracted from the NFT Feature definition. It's form must be..... | Our goal will be to generate a set of maplets over the NFT site plus 1/2 maplet boarder at a GSD that is 1/2 of the requested NavCam pixel size. Obviously, images 27-30 will not work. We will create one CSV file for each week. Then this file will be exported and run through a program (TBD) that will create the input files for bigmap and make_scriptT. The general format will be string-ID-GSD.sufix. * NFT-10021-8.IN with the bigmap called <idGSD.MAP> (e.g. MAPFILES/100218.MAP and MAPFILES/100216.MAP) * tileSeed-10021-8.seed where the 1st line uses the GSD from the CSV file When we run the program (TBD), it will generate the bigmap input and seed files for all records in the file (which should be about 18). Then we can use these as the inputs for the base tiling, intermediate tiling, and final tiling. We assume that 14cm can jump to 5cm and that 14cm exists everywhere. Assuming the standard for NFT features of width of 100, we will use a Q=50 (width of 101). We will tile at a Q=150, which would give 1/2 a maplet over all the edges. The core NFT region would be covered by a 3x3 and with the "margin" it will become 5x5, which means there is a full four maplets over the exact NFT unit. Each week, we will receive a NFT feature description of less than 20 features. We must take these definitions and fold them into a CSV file that includes the following || NFT ID || Picture name (raw) || SPC Image Name || Sample || Line || GSD [cm] || Q (half width) || Notes || || 10021 || 20191028T121532.002.fits || P601324232A3 || 150|| 801 || 6.3 || 100 || || etc. || == Resolution Steps == Steps of resolution -- Note, we will use the exact decimal value for the final tiling || GSD|| Base || Low || Medium || Final || ||16|| || || || 8 || ||14|| || || || 7 || ||12|| || || || 6 || ||10|| || || || 5 || ||8|| || || || 4 || ||7|| || || || 3.5 || ||6|| || || || 3 || ||5||5 || || || 2.5 || ||4||5 || || || 2 || ||3.5||5 || 2 || || 1.75 || ||3 ||5 || 2 || || 1.5 || ||2.5||5 || 2 || || 1.25 || ||2 ||5 || 2 || || 1 || ||1.5||5 || 2 || 1 || 0.75 || ||1 ||5 || 2 || 1 || 0.5 || ||.5 ||5 || 2 || 1 || 0.5 || |
| Line 9: | Line 49: |
== Distribution names == |
|
| Line 20: | Line 63: |
| {{ FILE=Img11 mv whatever $FILE.TXT }} |
----- == Running == Start in the working directory and copy the control file that you created into the nftConfig directory {{{ FILE=feature-img11 mkdir -p nftConfig cp whatever nftConfig/$FILE }}} |
| Line 28: | Line 80: |
| == Build scripts | == Build scripts == |
| Line 30: | Line 82: |
| {{ python nftRip.py $FIILE.txt }} |
{{{ python /opt/local/spc/bin/nftRip.py $FILE }}} |
| Line 40: | Line 92: |
Parameter File
Our goal will be to generate a set of maplets over the NFT site plus 1/2 maplet boarder at a GSD that is 1/2 of the requested NavCam pixel size. Obviously, images 27-30 will not work.
We will create one CSV file for each week. Then this file will be exported and run through a program (TBD) that will create the input files for bigmap and make_scriptT. The general format will be string-ID-GSD.sufix.
NFT-10021-8.IN with the bigmap called <idGSD.MAP> (e.g. MAPFILES/100218.MAP and MAPFILES/100216.MAP)
- tileSeed-10021-8.seed where the 1st line uses the GSD from the CSV file
When we run the program (TBD), it will generate the bigmap input and seed files for all records in the file (which should be about 18). Then we can use these as the inputs for the base tiling, intermediate tiling, and final tiling. We assume that 14cm can jump to 5cm and that 14cm exists everywhere.
Assuming the standard for NFT features of width of 100, we will use a Q=50 (width of 101). We will tile at a Q=150, which would give 1/2 a maplet over all the edges. The core NFT region would be covered by a 3x3 and with the "margin" it will become 5x5, which means there is a full four maplets over the exact NFT unit.
Each week, we will receive a NFT feature description of less than 20 features. We must take these definitions and fold them into a CSV file that includes the following
NFT ID |
Picture name (raw) |
SPC Image Name |
Sample |
Line |
GSD [cm] |
Q (half width) |
Notes |
10021 |
20191028T121532.002.fits |
150 |
801 |
6.3 |
100 |
||
etc. |
Resolution Steps
Steps of resolution -- Note, we will use the exact decimal value for the final tiling
GSD |
Base |
Low |
Medium |
Final |
16 |
|
|
|
8 |
14 |
|
|
|
7 |
12 |
|
|
|
6 |
10 |
|
|
|
5 |
8 |
|
|
|
4 |
7 |
|
|
|
3.5 |
6 |
|
|
|
3 |
5 |
5 |
|
|
2.5 |
4 |
5 |
|
|
2 |
3.5 |
5 |
2 |
|
1.75 |
3 |
5 |
2 |
|
1.5 |
2.5 |
5 |
2 |
|
1.25 |
2 |
5 |
2 |
|
1 |
1.5 |
5 |
2 |
1 |
0.75 |
1 |
5 |
2 |
1 |
0.5 |
.5 |
5 |
2 |
1 |
0.5 |
Output it to a file
Distribution names
Names
Img11
Img18
Img23a
Img23b
Img27a
Img27b
Img30a
Img30b
Running
Start in the working directory and copy the control file that you created into the nftConfig directory
FILE=feature-img11 mkdir -p nftConfig cp whatever nftConfig/$FILE
Build scripts
python /opt/local/spc/bin/nftRip.py $FILE
This creates the nftCtl directory. It includes the bigmap definition for tiling and the seed file for the resolution.
nftBigmap-<ID>-<res>.IN
nftTile-<ID>-<res>.seed
Based on the resolution, one to four files are created (options are: 5cm, 2cm 1cm and 1/2GSD). Start with the lowest resolution, the largest number, and do the rest of the procedures on them.