Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

TODOs (updated 12/10/2024)

  1. Steps in rawtherapee for SemiF (vid)

  2. Reformat Command line instructions for SemiF

  3. Minor cleaning/formatting for both Field and SemiF

  4. Flow chart of data transfer and processing for both Field and SemiF (MattMatthew Kutugata) , could be a general flowchart placed in the main preprocessing page.

    1. Courtney Belcher Courtney Belcher could give it a shot

Backlog Spreadsheet:

Lref gdrive file
urlhttps://docs.google.com/spreadsheets/d/18fwdSJxMy1WjCBCSCTb3uERj5D32H5jmBEh5dVpvrog/edit?gid=1066600493#gid=1066600493

...

When downloading a Semifield batch, we need to copy it It copies over to the local user from the NFS Lockers.

Code Block
cd ..
cd psa_images/semifield_tools/
screen -R <batch_name>
python3 copy_from_lockers_test.py <batch_name>

Semifield batches can take anywhere from a few minutes to half an hour to copy over, depending on the batch size. This is why it It is important to open a new screen for copying. Be sure only Only to copy one or two batches at a time within their respective screens to avoid disk space problems.

...

If the batch has either been completed copying or there has been an error copying, there will be an input line. If there is no input line, the process has not completed.

...

It is important to check if the copied batch was brought to the local user entirely.

We must know the # of images in the original batch. This can be checked using Use this command line:

breakoutMode
Code Block
wide
ls /mnt/research-projects/s/screberg/longterm_images2/semifield-upload/<batch>/*.ARW | wc -l

for example ls /mnt/research-projects/s/screberg/longterm_images2/semifield-upload/MD_2024-07-02/*.ARW | wc -l

output: 560

- Check the number Sometimes this command may need to be run two or three times before it output the correct value.

Check the # of images in the local directory after moving download has completed.

(Moving files from longterm storage to the local working directory. (, before you run the the …PIPLINE.pypipeline). This

*The output should be equal to the same as the above command. But ; should equal be 0 after running the pipeline

Use this command:

breakoutMode
Code Block
wide
ls /home/psa_images/temp_data/semifield-upload/<batch>/*.ARW | wc -l

...

After running the pipeline, check if all the ARW files have converted to JPGs and have moved to the longterm “developed” storage.

Use this command:

Code Block
ls /mnt/research-projects/s/screberg/longterm_images2/semifield-developed-images/<batch>/images/*.jpg | wc -l

Example: MD_2024-07-02

Code Block
 ls /mnt/research-projects/s/screberg/longterm_images2/semifield-upload/MD_2024-07-02/*.ARW | wc -l

output: 560

Code Block
ls /home/psa_images/temp_data/semifield-upload/MD_2024-07-02/*.ARW | wc -l

output (before running the pipeline): 560

output (after running the pipeline): 0

...

Code Block

...

ls /mnt/research-projects/s/screberg/longterm_images2/semifield-developed-images/

...

MD_2024-07-02/images/*.jpg | wc -l

output (after running the pipeline): 560

Trouble shooting:

If developed jpgs are not in the longterm storage, check to see if they’re still in the local temp_data outputs folder:

  • Check for

...

  • jpgs:

Code Block
ls /

...

home/psa_images/temp_data/semifield-

...

outputs/MD_2024-07-

...

26/images/*.jpg | wc -l

output (after running the pipeline): 560

- These 3 commands should output the same number.

- check for same number of .pp3 files (how you know they’ve been developed):

Code Block
ls /home/psa_images/temp_data/semifield-outputs/MD_2024-07-26/images/*.pp3 | wc -l

If they’re both present and have the same number, we know they’ve been successfully preprpocessed, but may not have been successfully move to the longterm locker storage location.

  • If there is an “Assertion Error”, try going into RawTherapee, and create & save the profile again.

2. Color Profiling in RawTherapee

...

Code Block
./RawTherapee_5.8.AppImage

...

RawTherapee will launch in an separate window , opening and open to the most recent profile that has been worked on. Select the appropriate batch and allow it to load. Scroll through making and make a mental note if some images are out of the ordinary (i.e. too bright, too dark, out of focus, etc.).

...

2.1 Creating a color profile

Our goal when creating a color profile is to have every image look similarly to the rest of the batch. When RawTherapee launches, it will bring us to the last batch we worked on by default. Be sure to navigate to the intended batch. Note when there is more than one folder within the batch. We must adjust every image in each folder before sending the batch into the pipeline.

It is good practice to scan through all images to get an idea of what they look are looking like, if there are any outliers, or anything else to make note of.

2.2 Look for a Color Checker

We want to use an image with a color checker, if one is available within the batch. Choose the most average looking picture (lighting and color-wise). If they all look reasonably similar, choose any of the options.

...

. It is preferred to select an average image with both a color checker and biomass. If there is no biomass present, choose an average image with a color checker.

...

*In Semifield applications, we typically use a smaller , Color Checker lanyard is typically used. The Field Color Checker may might be used instead, but the larger smaller one is preferred for this application. Either is acceptable.

2.

...

12 Bring in a

...

Recent profile & Color Picker

...

To bring in a recent profile, find the folder icon towards the top right of the screen, located to the left of the save button. This will open a window containing a list of saved profiles within the local user. Choose the most recent date in relation to the image being worked on now. It is helpful to use the name & date modified arrows, making it easier to find most recent profiles.

...

Once a previous profile is loaded in and applied, use the color picker tool. The Color Picker tool is found on the tool bar above the working image or using use the White Balance tab on the panel to the right. Choose “Pick”.

...

Only one square on the Color Checker is used for in this application. Referring to the image above, the gray we want is residing two squares above the black is the color to use. Use this gray for every profile you make.When finished, be sure to choose . Choose the hand icon to return to normal cursor mode.

2.

...

13 Adjust exposure & saturation

...

Now, we navigate into the Exposure tab. This is the only tab we will work used in preprocessing, aside from the tab to access the Color Picker. There are only a few helpful settings to toggle here.

Our The goal is to create an image that looks most closely like a real-life view of these plants. Our eyes are The human eye is the most accurate check, but it can be helpful to keep an eye on reference the color graph in located on the top left that of the scree. It shifts when settings are changed. A good rule of thumb is for the peak of the three curves to land near this region of the graph.

...

*Laptop screens and Monitor settings will impact what we are working onperception of images. Try to always use the same screen when creating color profiles.

  • Exposure Compensation & Highlight Compression

    • These two go hand-in-hand. Exposure compensation should always be set to slightly more than Highlight Compression

  • Lightness

    • Has a similar effect to Exposure Compensation

  • Saturation

    • Toggle keeping in mind the intensity of colors on the color checker.

3. Running the pipeline

...

** Don't run >3 batches in the pipeline at once. This applies to both Semifield and Field combined. **

Profiling can be done and batches can be prepared for the pipeline

...

When , but wait to run them until another batch finished.

After the color profile has been saved, we must send it through the pipeline. Be sure to be navigated to the Semifield folder and make a new screen, use uppercase r (-R). If returning to an already existing screen, use lowercase r (-r) with the appropriate screen name.

...

If there is an indication the pipeline is finished running, we want to crosscheck the # of images in the original batch with the # of JPGs and PP3s created.

We can use both of these lines respectively:

breakoutMode
Code Block
wide
ls /mnt/research-projects/s/screberg/longterm_images2/semifield-developed-images/<batch>/images/*.jpg | wc -l
breakoutMode
Code Block
wide
ls /mnt/research-projects/s/screberg/longterm_images2/semifield-developed-images/<batch>/images/*.pp3 | wc -l

And compare to the # of ARWs using this:

Code Block
breakoutModewide
ls /mnt/research-projects/s/screberg/longterm_images2/semifield-upload/<batch>/*.ARW | wc -l

As long as the output # we get from each of these commands are equivalent, we know we have successfully applied the color profile has successfully been applied to every image in the batch.

If the # of JPGs and PP3s are not equivalent to the original # of images, try running the pipeline again within the same screen. Double check the name of the batch that was typed in, this is where errors are likely to happen. Also, be sure to be navigated to the Semifield folder. If we are within navigated to the Field folder, the pipeline will not be successful.

...

Available batches:

wide
Code Block
breakoutMode
ls /mnt/research-projects/s/screberg/longterm_images2/semifield-upload/ -lh

# of images in batch:

breakoutMode
Code Block
wide
ls /mnt/research-projects/s/screberg/longterm_images2/semifield-upload/<batch>/*.ARW | wc -l

# of JPGs processed:

wide
Code Block
breakoutMode
ls /mnt/research-projects/s/screberg/longterm_images2/semifield-developed-images/<batch>/images/*.jpg | wc -l

# of PP3 files created:

wide
Code Block
breakoutMode
ls /mnt/research-projects/s/screberg/longterm_images2/semifield-developed-images/<batch>/images/*.pp3 | wc -l

...