Have been manually replacing "mock" with, say, "wild-type" in use_mock_atlas_scalar.py then running it with the --pairwise-output option to create e.g., wild-type.tsv from wild-type.pickle. To streamline that, would be nice to have, say, export_atlas_scalar.py where the atlas can be specified. Perhaps I am overlooking something, but I went ahead and forked this repo and created such a script.
Will attach a forked pull request next, but really all it is is another script, export_atlas_scalar.py in the scripts dir, that adds an --atlas option to use_mock_atlas_scalar.py. Is tempting to just attach it here, but I might as well go through with the PR. I could use the practice!
Have been manually replacing "mock" with, say, "wild-type" in
use_mock_atlas_scalar.py
then running it with the--pairwise-output
option to create e.g.,wild-type.tsv
fromwild-type.pickle
. To streamline that, would be nice to have, say,export_atlas_scalar.py
where the atlas can be specified. Perhaps I am overlooking something, but I went ahead and forked this repo and created such a script.Will attach a forked pull request next, but really all it is is another script,
export_atlas_scalar.py
in the scripts dir, that adds an--atlas
option touse_mock_atlas_scalar.py
. Is tempting to just attach it here, but I might as well go through with the PR. I could use the practice!