Skip to content

Bathymetry for next release playground : Candiate 1. Axial Seamount #202

Merged
woensug-choi merged 1 commit into
Field-Robotics-Lab:masterfrom
woensug-choi:axial_seamount_simple
Feb 22, 2022
Merged

Bathymetry for next release playground : Candiate 1. Axial Seamount #202
woensug-choi merged 1 commit into
Field-Robotics-Lab:masterfrom
woensug-choi:axial_seamount_simple

Conversation

@woensug-choi
Copy link
Copy Markdown
Collaborator

@woensug-choi woensug-choi commented Feb 15, 2022

Axial Seamount

image
image

Launch command

roslaunch dave_demo_launch dave_Axial_Seamount_demo.launch

New files in this PR

  • world file : dave_Axial_Seamount.world
  • launch file : dave_Axial_Seamount_demo.launch
  • Model : dave/models/dave_object_models/models/AxialSeamountPatch

Statistics

  • Origin of the source data : https://www.marine-geo.org/tools/datasets/30219
    Clague, D.; Caress, D. and J. Paduan, (2022). Preliminary 1-meter resolution
    bathymetric model (ESRI ASCII grids) for the summit region of Axial
    Seamount, version as of 10 March 2021. IEDA. doi:10.26022/IEDA/330219
  • Resolution : 75 cm
  • Latitude : 46.035 ~ 46.05
  • Longitude : -129.93 ~ -129.914
  • Size of the patch : (Lat, Lon) = (0.015, 0.016) = Approx 1000 x 1000 meters)
  • Maximum Height : -2139.0134277
  • Minimum height : -3.4E+38 (garbage data inside)
  • Number of vertices of original data = 3072 x 2560

Conversion method

  • mkbaty.py automation script at https://github.com/Field-Robotics-Lab/Bathymetry_Converter
  • Flags parameters used inside the script :
    • ONE_TILE_AT_ORIGIN : True
    • SIMPLIFICATION_LEVEL : 3 ( if set 0; without any simplification, the mesh OBJ would be 350MB~)
      • Size of the OBJ file is 25 MB
  • Parameters used:
    • PREFIX = AxialSeamountPatch

    • Ranges

      • STARTLON = -129.930
      • STARTLAT = 46.035
      • ENDLON = -129.914
      • ENDLAT = 46.050
    • Color texture (color.txt)

      -2190 213 62 79
      -2210 244 109 67
      -2230 254 224 139
      -2245 255 255 191
      -2260 230 245 152
      -2275 171 221 164
      -2290 102 194 165
      -2295 50 136 189
      -2300 94 79 162
      -2315 77 77 77
      -2330 26 26 26
      

@j-herman Are you going to make a wiki? a page for the conversion tutorial? (as I remember from your reply to Brian's mail). I had to introduce bunch of mesh simplification methods in the mkbathy.py script. You may give it a look :)

@woensug-choi
Copy link
Copy Markdown
Collaborator Author

woensug-choi commented Feb 15, 2022

Tiled version

@woensug-choi woensug-choi changed the title Axial Seamount Bathymetry for next release playground Candiate 1: Axial Seamount Bathymetry for next release playground Feb 15, 2022
@woensug-choi woensug-choi changed the title Candiate 1: Axial Seamount Bathymetry for next release playground Bathymetry for next release playground : Candiate 1. Axial Seamount Feb 15, 2022
@j-herman
Copy link
Copy Markdown
Contributor

@woensug-choi I was just going to write up a page for using a different/ higher resolution file instead of the sandy bottom heightmap in dave_demo.launch. Since we don't use the tiling and plugin with the current sandy bottom model that conversion is pretty straightforward.
This new example looks great! I'll run it and see how it goes.

Copy link
Copy Markdown
Contributor

@j-herman j-herman left a comment

Choose a reason for hiding this comment

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

The world looks great!

@woensug-choi woensug-choi requested a review from bsb808 February 16, 2022 02:49
@woensug-choi
Copy link
Copy Markdown
Collaborator Author

@j-herman Thank you for testing it out! Could you test the other candidate #203 too?

I wonder how we are going to distribute high-resolution bathymetry data. I've put some effort to reduce it to around 20MB for this and another candidate. Github allows a maximum 40 MB file unless we adopt lf (https://docs.github.com/en/repositories/working-with-files/managing-large-files)

For more higher-level discussion, as @bsb808 mentioned in the mail, I understood as this playground wrap-up would not be included in the next release nor the end of march timeline. But worth introducing to them how things will be integrated into this playground (with doneness metric). Meanwhile, your new page preparation will be included in the next release or end of march timeline since it is a definitive demonstration for proof of collaborative possibility with Makai. Am I correct?

@Yadunund
Copy link
Copy Markdown
Member

I wonder how we are going to distribute high-resolution bathymetry data.

One thing we could do is create a script that 1) downloads the dataset 2) runs the Batymetry_Converter on the dataset and 3) installs the output to a share directory at build time. Once we have such a script, we would just need to modify the CMakeLists.txt file for the worlds package such that its executes during catkin build. This has worked well for other projects where worlds needed to be auto-generated and where large 3D models needed to be made available to downstream users. Happy to discuss this further if required.

@j-herman
Copy link
Copy Markdown
Contributor

For more higher-level discussion, as @bsb808 mentioned in the mail, I understood as this playground wrap-up would not be included in the next release nor the end of march timeline. But worth introducing to them how things will be integrated into this playground (with doneness metric). Meanwhile, your new page preparation will be included in the next release or end of march timeline since it is a definitive demonstration for proof of collaborative possibility with Makai. Am I correct?

I thought we were trying to get everything put together by the end of March, including the integrated demo, but maybe I misunderstood. It's a lot to get done by then!
I've put together a demo and drafted a wiki on creating a custom seafloor that works more or less like what we already sent to the sponsor via other means, so we will have a record here. Not sure whether we'll want to incorporate that example but there's a PR in case anyone wants to play around with a new world.

@woensug-choi
Copy link
Copy Markdown
Collaborator Author

Merging it now. Will make a wiki page for both Axial Seamount and Santorini today.

@woensug-choi woensug-choi merged commit 564c9f8 into Field-Robotics-Lab:master Feb 22, 2022
@woensug-choi
Copy link
Copy Markdown
Collaborator Author

@woensug-choi woensug-choi deleted the axial_seamount_simple branch February 23, 2022 08:29
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.

3 participants