Skip to content

Conversation

@ConnectedSystems
Copy link
Collaborator

@ConnectedSystems ConnectedSystems commented Apr 6, 2024

Expanded documentation and added:

  • run_init()
  • reef_areas()
  • collect_rep_results!()

ReefModEngine.jl now checks if the user-provided path is valid before attempting to associate/load RME constants.
Previously the user input was trusted. If an incorrect path was given, there was no way of correcting it and the Julia session would need to be restarted.

An alternate approach to determining deployment densities is also included:

set_outplant_deployment!("outplant_iv_2026", "iv_example", 100_000, 2026, target_reef_areas_km²)

# vs

set_outplant_deployment!("outplant_iv_2026", "iv_example", 100_000, 2026, target_reef_areas_km², 6.8)

The first, without a density value specified, will attempt to calculate an appropriate density for the given reef area that maintains the set simulation grid size (defaulting to 10x10 - this correlates with the RMFAST10 processing option in ReefMod Engine).

The second is the previous approach, which assumes the specified density is a hard requirement, and attempts to determine an appropriate grid size (up to 100x100) to adequately represent it. Note that longer run times should be expected with larger grid sizes.

@ConnectedSystems ConnectedSystems merged commit 9c63049 into main Apr 7, 2024
@ConnectedSystems ConnectedSystems deleted the more-support branch April 7, 2024 05:23
@ConnectedSystems ConnectedSystems mentioned this pull request Apr 7, 2024
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.

2 participants