Keeping everything related to the standalone driver in the test/ subdirectory doesn't really make sense, nor do the current contents of regression_tests/ (call_compute_subroutines/ really is a regression test, and gen_settings_file/ could probably be turned into one fairly easily, but everything else is effectively generating documentation). I suggest the following:
rename tests/ -> standalone_MARBL
Under standalone_MARBL/, keep driver_exe/, driver_src/, input_files/, obj/, and python_for_tests/
Move bld_tests/, regression_tests/, and unit_tests/ to a new standalone_MARBL/tests/ subdirectory
Create a new standalone_MARBL/tests/doc_gen/ subdirectory
It would be great to tie doc_gen/ subdirectories into the actual generation of the HTML documentation, though I don't know how feasible that is.
Some thoughts that might be worth considering:
Maybe driver_exe/ and obj/ belong in a standalone_MARBL/bld_out/ subdirectory or something
standalone_driver/ instead of standalone_MARBL/? The point is that no external GCM is needed for anything under this directory, it's meant to provide simple test cases and examples
Keeping everything related to the standalone driver in the
test/
subdirectory doesn't really make sense, nor do the current contents ofregression_tests/
(call_compute_subroutines/
really is a regression test, andgen_settings_file/
could probably be turned into one fairly easily, but everything else is effectively generating documentation). I suggest the following:tests/
->standalone_MARBL
standalone_MARBL/
, keepdriver_exe/
,driver_src/
,input_files/
,obj/
, andpython_for_tests/
bld_tests/
,regression_tests/
, andunit_tests/
to a newstandalone_MARBL/tests/
subdirectorystandalone_MARBL/tests/doc_gen/
subdirectoryIt would be great to tie
doc_gen/
subdirectories into the actual generation of the HTML documentation, though I don't know how feasible that is.Some thoughts that might be worth considering:
driver_exe/
andobj/
belong in astandalone_MARBL/bld_out/
subdirectory or somethingstandalone_MARBL/driver_src
->standalone_MARBL/src
?standalone_driver/
instead ofstandalone_MARBL/
? The point is that no external GCM is needed for anything under this directory, it's meant to provide simple test cases and examples