The tmd_2021.csv column names are not always in the same order even though the set of columns is the same. For example, in a recent excercise in which I created 4 variants of tmd output, under 4 different sets of assumptions, the names of the first 3 of the 213 columns were:
This defeats software such as R's vroom, which can read and combine a set of uniformly-structured csv files rapidly in parallel, which is useful when comparing multiple versions of tmd output prepared with different assumptions.
The alternative is to read the files one by one and combine them, which is considerably slower.
Not a big deal, but at some point, @nikhilwoodruff, it would be great if you could force the structure (column order) of tmd_2021.csv to be consistent from run to run.
The tmd_2021.csv column names are not always in the same order even though the set of columns is the same. For example, in a recent excercise in which I created 4 variants of tmd output, under 4 different sets of assumptions, the names of the first 3 of the 213 columns were:
This defeats software such as R's vroom, which can read and combine a set of uniformly-structured csv files rapidly in parallel, which is useful when comparing multiple versions of tmd output prepared with different assumptions.
The alternative is to read the files one by one and combine them, which is considerably slower.
Not a big deal, but at some point, @nikhilwoodruff, it would be great if you could force the structure (column order) of tmd_2021.csv to be consistent from run to run.