Closed haowang-bioinfo closed 2 years ago
would be nice to mention in the Readme or the release text what version of Human-GEM this is based. Also, there is an update of orthologs, perhaps the reason behind that should also be stated.
Good point, will include this info to the release message
Very nice, @haowang-bioinfo!
I don't think I've ever seen this before though:
I don't think I've ever seen this before though
this is probably due to the huge raw data of ortholog pairs downloaded from Alliance of Genomes, any thoughts in avoiding this?
I think it's ok - it almost seems like a bug; only 8 files changed. The 8... fell over... or something.
I think it's ok - it almost seems like a bug
Instead of updating the huge raw data of ortholog pairs, a more decent way might be just logging the extracted pairs in tsv
format
To release new Mouse-GEM
with all the changes, a new Human-GEM
release probably should also be pushed?
Instead of updating the huge raw data of ortholog pairs, a more decent way might be just logging the extracted pairs in
tsv
format
Very good idea!
To release new
Mouse-GEM
with all the changes, a newHuman-GEM
release probably should also be pushed?
Another option is to link either the Human-GEM PR that was used, or the merge commit hash https://github.com/SysBioChalmers/Human-GEM/commit/ff109f2283e06bc741ccd991c87ecc11a87a17a6 .
merge commit hash https://github.com/SysBioChalmers/Human-GEM/commit/ff109f2283e06bc741ccd991c87ecc11a87a17a6 .
this is an easier option
Main improvements in this PR:
p
tox
, to sync with changes made in Human-GEM PR 3415.1.0
.gitattributes
to ensure consistent LF (\n) line endingsmaster
-->main
,devel
-->develop