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

Raise MemoryError proactively in certain cases #2

Open
dbetchkal opened this issue Nov 10, 2020 · 1 comment
Open

Raise MemoryError proactively in certain cases #2

dbetchkal opened this issue Nov 10, 2020 · 1 comment
Labels
enhancement New feature or request

Comments

@dbetchkal
Copy link
Owner

In NMSIM_InputOutputTools.tbx, it seems appropriate to anticipate that some users may try to create projects so large that NMSIM will crash. This should be handled in advance.

There are two prerequisites:

  1. What is NMSIM's memory limit? (Presumably constant.) Convert to a maximum area.
  2. How to extract the area of the Study Area Polygon from the Attribute Table using SearchCursor? Should be pretty easy.
@dbetchkal dbetchkal added the enhancement New feature or request label Nov 10, 2020
@dbetchkal dbetchkal changed the title Raise error when Study Area Polygon exceeds a certain size Raise MemoryError proactively in certain cases Sep 26, 2022
@chevelle3504speed
Copy link
Collaborator

chevelle3504speed commented Sep 26, 2022

Additionally, if modeling slow-moving sources such as ATVs and ORVs, the speed of the vehicle and length of trail/trajectory appear to have sizeable effects on software memory limitations. If NMSim crashes when attempting to generate an output (.tig) file, create a new trajectory file and increase vehicle speed and/or reduce length of trail/path to be modeled before reattempting output file generation. Speeds of <8 mph have been problematic on path/trajectories 18 km long in early testing.

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

No branches or pull requests

2 participants