Changes between Version 209 and Version 210 of Procedures/NewDataArrival

Timestamp:

Jun 18, 2026, 4:08:49 PM (4 months ago)

Author:

mark1

Comment:

--

Procedures/NewDataArrival

@@ -104 +104 @@
 
 
-=== Logsheet and Remaining Steps===
+== Logsheet and Remaining Steps==
 
  * Look at the logsheet included and verify that we have copies of all relevant data mentioned there.
@@ -110 +110 @@
  * Verify all details on the logsheet (esp. PI) by calling/emailing NERC-ARF Ops making them aware of the projects that have been unpacked - the application form and logsheet are not sufficient proof, nor do they track any changes in PI over the lifetime of the application.
 
-'''To use the 2021 logsheet generator follow these steps here, or scroll further to find instructions for the old version of logsheet generator.'''
-
-To create a logsheet is run in 3 stages to give greatest control of input/output. The first stage is to generate csv tables of the information to go into the logsheet. Then you create an image of the overview of flightlines, and finally you can render an HTML and PDF version of the data.
+'''To use the current logsheet generator follow these steps here, or scroll further to find instructions for the old version of logsheet generator.'''
+
+To create a logsheet is run in 3 stages to give greatest control of input/output. 
+1. The first stage is to generate csv tables of the information to go into the logsheet. 
+2. Then you create an image of the overview of flightlines, and then ...
+3. finally you can render an HTML and PDF version of the data.
 
 Example commands:
@@ -118 +121 @@
 To create the CSV tables and get all the data together you pass the project directory, a sensor list to include in the logsheet and output directory (e.g. processing/logsheet)
 
-{{{generate_logsheet.py -p /users/rsg/arsf/arsf_data/2021/flight_data/sweden/Magic-2021_236_Kiruna -o /tmp/logsheet -s fenix -v}}}
-
-
-
-== Important note ==
-
-The hyperspectral config file must be found as {{{/processing/hyperspectral/yyyyjjjs.cfg}}} and might need to remove either fenix1k when creating a readme file for the owl sensor.
-
-
-To create an overview it is recommended to use the `byline` option to colour the flight lines, `--inset` to generate an inset in the image and `-A` to create an animated GIF (for the website)
+{{{generate_logsheet.py -p /users/rsg/arsf/arsf_data/2021/flight_data/sweden/Magic-2021_236_Kiruna -o /tmp/logsheet -s fenix ibis owl lidar -v}}}
+
+To create an overview it is recommended to use the `byline` option to colour the flight lines, `--inset` to generate an inset in the image and `-A` to create an animated GIF (for the website). If you have the logsheet csv files generated from step 1 above then you can use these:
+
+{{{generate_overview_for_logsheet.py -p /users/rsg/arsf/arsf_data/2021/flight_data/sweden/Magic-2021_236_Kiruna -o /tmp/logsheet/overview.png  -c byline -A /tmp/logsheet/overview.gif --inset --csv /path/to}logsheet_flightline_table.csv}}}
+
+else you can run like this by specifying a sensor:
 
 {{{generate_overview_for_logsheet.py -p /users/rsg/arsf/arsf_data/2021/flight_data/sweden/Magic-2021_236_Kiruna -o /tmp/logsheet/overview.png -s fenix -c byline -A /tmp/logsheet/overview.gif --inset}}}
@@ -198 +198 @@
  * Click 'fill post manual'. This will calculate the values for the green fields based on the values you have entered into the yellow fields. You should also check that these fields look correct. If the flight was flown over midnight, you may need to correct them.
 
-[[BR]]
+
+=== Important note ===
+
+The hyperspectral config file must be found as {{{/processing/hyperspectral/yyyyjjjs.cfg}}} and might need to remove either fenix1k when creating a readme file for the owl sensor.
+
+
+[[BR]]