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

[ENHANCEMENT] RUN_UAM should generate multiple samples #1

Open
aweinert-MIT opened this issue Apr 14, 2020 · 0 comments
Open

[ENHANCEMENT] RUN_UAM should generate multiple samples #1

aweinert-MIT opened this issue Apr 14, 2020 · 0 comments

Comments

@aweinert-MIT
Copy link
Member

Instructions

Read the instructions and fill out your responses at the bottom.

Relation

Is your feature request related to a problem? Please describe. Please provide a clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Description

A clear and concise description of what you want to happen.

Alternatives

A clear and concise description of any alternative solutions or features you've considered.

Additional context

Add any other context or screenshots about the feature request here.

FILL ME OUT

Relation

RUN_UAM.jl currently generates one sample. This is insufficient for encounter set generation.

Description

Modify the run script to generate and output multiple samples. To promote good load balancing, generated files should be organized in subdirectories based on initial altitude or some other criteria. For example, if 100,000 samples are to be generated, a single directory should not be used for all 100,000 samples.

For reproducibility, the random seed should be set and unique for each sample.

Alternatives

A simple for loop that sets the random seed and calls generate_trajectory_file is a good starting point. Parallel computing may be required to generate a large set of unique samples.

Additional

To support encounter set development, at least 100,000 unique samples should be efficiently generated.

@aweinert-MIT aweinert-MIT transferred this issue from Airspace-Encounter-Models/em-overview May 15, 2020
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

No branches or pull requests

1 participant