-
Notifications
You must be signed in to change notification settings - Fork 2
Code structure
Maurits Kok edited this page Apr 29, 2021
·
9 revisions
You can run the simulation through the script mit_plan_modular.m
or with the GUI MitC_app.mlapp
. Both scripts call the code present in the folder /modules
. As a best practice when updating the code, make sure the code is functional with mit_plan_modular.m
first, before updating the GUI.
You can run all tests bu executing the function run_tests.m
.
-
/modules
contains the separate modules called in the GUI -
/bin
contains helper functions -
/plotting
contains all scripts related to plotting
mitc
| MitC.prj
| MitC_app.mlapp
| mit_plan_modular.m
| run_tests.m
|
|---bin
| allpaths.m
| calculate_no_correlation.m
| cost_cdfdist.m
| cost_pdfdist.m
| draw_random_numbers.m
| find_dependencies.m
| find_missing_predecessors.m
| fitting.m
| rand_pert.m
| randraw.m
| remove_missing.m
| remove_nan.m
| type_error.m
| unique_doubles_from_cell.m
| verify_fieldnames.m
|
|---modules
| export_results.m
| find_critical_path.m
| generate_paths.m
| import_project.m
| mitc_simulation.m
| opt_mit_lin.m
| parse_data.m
| verify_filepath.m
| verify_raw_data.m
|
|---plotting
export_fig.m
plot_cdf.m
plot_cost_distribution.m
plot_freq_activity.m
plot_freq_mitigation.m
plot_freq_paths.m
plot_network.m
Project details
FAIR
MATLAB
- Code Structure
- Use Cases
- Project Data
- Variable Names
- GUI Architecture
- Packaging and Compiling
- Testing
Git and GitHub