write-experiment-config

To create a valid experiment config JSON for a FRESCO pipeline run, you must populate all required fields including run_id, dataset_version, input_root, output_root, clusters, date_range, random_seed, write_manifests, and write_validation_reports, then commit the file to the experiments/<EXP-XXX>/config/ directory.

Mandatory fields in a FRESCO experiment config include run_id, dataset_version, input_root, output_root, clusters, date_range, random_seed, write_manifests, and write_validation_reports to ensure structure validation and reproducibility.

You should store the FRESCO experiment config JSON file under the strictly enforced experiments/<EXP-XXX>/config/ directory path to maintain repository conventions and ensure reproducible pipeline runs.

Yes, you can use remote production templates for your FRESCO experiment config, as the configuration process supports both local and remote production templates for generating validated JSON files.

Your FRESCO pipeline may fail before starting a run if the experiment config JSON is missing mandatory fields or stored in an incorrect file location, as the system enforces strict structure validation and repository path conventions.

Yes, you need to commit the experiment config JSON to the prescribed experiments/<EXP-XXX>/config/ path before starting the FRESCO pipeline run to prevent missing fields and misconfigurations.