-
Notifications
You must be signed in to change notification settings - Fork 14
Output directory and files
Rajendra Adhikari edited this page May 12, 2020
·
9 revisions
The eagle output directory structure, what various files mean.
Whatever folder is specified in output_directory in the yml file
- dask_scheduler_##.josn <---- dask details
- dask_scheduler_##.out <--- dask details
- job##.josn <--- which simulation belong to which job
- job.out-## <--- console/log output of buildstockbatch when running simulations contained in job ##
- postprocessing.out <-- console/log output of postprocessing
- sampling.out <--- console/log output of sampling
- weather <--- weather files
- housing_characteristics <--- the housing characteristics tsv files and sampled buildstock_csv files are here
- results <--- simulation and postprocessing output folder
- parquet <--- postprocessed and combined timeseries parquet files
- results_csvs <--- postprocessed results_csv files
- simulation_output <--- raw simulation output for each buildings
- baseline <--- this is the equivalent of results_csvs but in parquet format
- timeseries <--- the timeseries parquet files live here
- results_up##.csv.gz <--- results csv file for upgrade ##, gunzipped.
- results_job##.json.gz <--- merged results.json simulation output files for all simulation that ran in job ##
- simulations_job##.tar.gz <--- collections of all the raw simulation output results (including data_point.zip) for all buildings that were part of job ##
- timeseries <--- folder containing the timeseries output for all buildings simulation, in parquet format