Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Support for DJI ILS corrections #52

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Conversation

joeyfranck56
Copy link
Contributor

@joeyfranck56 joeyfranck56 commented Oct 18, 2024

Add Support for DJI ILS data

What?

Why?

PR Checklist

  • Merged latest master
  • Updated version number
  • Version numbers match between package __version__ and pyproject.toml
  • All private git packages are at their newest version in both pyproject.toml and environment.yml
  • All git package version numbers match between pyproject.toml and environment.yml
  • dist/ImageryCorrector.exe and dist/GetCorrectionsCsv.exe have been rebuilt

Breaking Changes

@@ -22,4 +22,4 @@ dependencies:
# subpackage dependencies
# Sentera dependencies
- pip:
- git+https://github.com/SenteraLLC/py-image-metadata-parser.git@v1.18.1
- git+https://github.com/SenteraLLC/py-image-metadata-parser.git@add-dji-ils
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Will update after pushed to main

if make == "DJI":
return imgparse.get_irradiance(row.image_path)
else:
return imgparse.get_ils(row.image_path)[0]
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I need to compare the results from both of these options and maybe fallback on ILS values if the irradiance values are not there. The Irradiance values are much more consistent throughout the flight and from what I've read the irradiance values are based on sun angle and other info stored in the images from the DLS(Directional Light Sensor). There isn't much info that I've found that compares the 2 values and a lot of stuff I've found makes it seem like they are the same.

@@ -65,7 +65,7 @@ def extract_panel_bounds(image):
corners, ids, rejected_img_points = cv.aruco.detectMarkers(image, dictionary)

# if at least one marker detected
if ids is not None:
if ids is not None and (ids[0][0] == 23 or ids[0][0] == 63):
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was getting an error for aruco ID 157 detected and think I've seen customers with this issue, I looked up that ID and its super simple to idk maybe something in the Mavic 3 sensor writes that pattern and it is being picked up incorrectly. This will skip any images that have the wrong ID detected. The image I had was not even a calibration image.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant