Hardcoded paths in example configs

[daniszw]

We still have some hardcoded paths in example configs...

terratorch/examples/confs/dofa_sen1floods11_fcn.yaml

Line 13 in 8533704

save_dir: /dccstor/geofm-finetuning/carlosgomes/torchgeo_floods

terratorch/examples/confs/dofa_sen1floods11_fcn.yaml

Line 26 in 8533704

default_root_dir: /dccstor/geofm-finetuning/carlosgomes/torchgeo_floods

terratorch/examples/confs/dofa_sen1floods11_fcn.yaml

Lines 58 to 67 in 8533704

	train_data_root: /dccstor/geofm-finetuning/flood_mapping/sen1floods11/data/data/flood_events/HandLabeled/S2Hand/
	train_label_data_root: /dccstor/geofm-finetuning/flood_mapping/sen1floods11/data/data/flood_events/HandLabeled/LabelHand
	val_data_root: /dccstor/geofm-finetuning/flood_mapping/sen1floods11/data/data/flood_events/HandLabeled/S2Hand/
	val_label_data_root: /dccstor/geofm-finetuning/flood_mapping/sen1floods11/data/data/flood_events/HandLabeled/LabelHand
	test_data_root: /dccstor/geofm-finetuning/flood_mapping/sen1floods11/data/data/flood_events/HandLabeled/S2Hand/
	test_label_data_root: /dccstor/geofm-finetuning/flood_mapping/sen1floods11/data/data/flood_events/HandLabeled/LabelHand
	# these must be obtained by running terratorch/examples/scripts/convert_sen1floods11_splits.py on the original split csv files
	train_split: /dccstor/geofm-finetuning/flood_mapping/sen1floods11/splits/splits/flood_handlabeled/flood_train_data_S2.txt
	test_split: /dccstor/geofm-finetuning/flood_mapping/sen1floods11/splits/splits/flood_handlabeled/flood_test_data_S2.txt
	val_split: /dccstor/geofm-finetuning/flood_mapping/sen1floods11/splits/splits/flood_handlabeled/flood_valid_data_S2.txt

The same pattern can be seen in examples dofa_sen1floods11_uper.yaml and satlas_sen1floods11_uper.yaml

---

In these other examples we also have hardcoded paths:

terratorch/examples/confs/granite-wxc-merra2-downscale-small-config.yaml

Lines 100 to 103 in 8533704

	data_path_surface: /home/jalmeida/Projetos/terratorch/examples/scripts/merra-2/
	data_path_vertical: /home/jalmeida/Projetos/terratorch/examples/scripts/merra-2/
	climatology_path_surface: /home/jalmeida/Projetos/terratorch/examples/scripts/climatology/
	climatology_path_vertical: /home/jalmeida/Projetos/terratorch/examples/scripts/climatology/

terratorch/examples/confs/granite-wxc-merra2-downscale-small-config.yaml

Lines 132 to 135 in 8533704

	input_scalers_surface_path: /home/jalmeida/Projetos/terratorch/examples/scripts/climatology/musigma_surface.nc
	input_scalers_vertical_path: /home/jalmeida/Projetos/terratorch/examples/scripts/climatology/musigma_vertical.nc
	output_scalers_surface_path: /home/jalmeida/Projetos/terratorch/examples/scripts/climatology/anomaly_variance_surface.nc
	output_scalers_vertical_path: /home/jalmeida/Projetos/terratorch/examples/scripts/climatology/anomaly_variance_vertical.nc

terratorch/examples/confs/granite-wxc-merra2-downscale-small-config.yaml

Lines 150 to 153 in 8533704

	data_path_surface: /home/jalmeida/Projetos/terratorch/examples/scripts/merra-2/
	data_path_vertical: /home/jalmeida/Projetos/terratorch/examples/scripts/merra-2/
	climatology_path_surface: /home/jalmeida/Projetos/terratorch/examples/scripts/climatology/
	climatology_path_vertical: /home/jalmeida/Projetos/terratorch/examples/scripts/climatology/

terratorch/examples/confs/wxc-gravity-wave-ccc.yaml

Lines 34 to 35 in 8533704

	train_data_path: /dccstor/terratorch/users/rkie/gitco/terratorch
	valid_data_path: /dccstor/terratorch/users/rkie/gitco/terratorch

[Joao-L-S-Almeida]

@daniszw I replaced it with generic paths in #458.

[daniszw]

Thanks! I would also suggest having a similar pattern of paths in all examples, and remove any non-english words from paths (like "Projetos"). For example, many configs have something like:
<your_path_here> or <sen1floods11_root>/v1.1/data/flood_events/HandLabeled/S2Hand/; I would use something similar to keep consistency.