Show version information in vp reports#1070
Conversation
|
To do:
|
| version_info = [] | ||
| # First check if first replica has 'version.info' | ||
| p_1 = replica_paths[0] / ('version.info') | ||
| if not p_1.is_file(): |
There was a problem hiding this comment.
Are you checking if the file exists here? Perhaps p_1.exists() reads a bit more naturally if so
|
Hi @RosalynLP, instead from the Edit: A fit that contains this .json file is |
|
Thanks @scarlehoff, will do - yep I didn't see these before as I was looking at an older fit. |
|
Greetings from your nice fit 🤖 !
Check the report carefully, and please buy me a ☕ , or better, a GPU 😉! |
|
Greetings from your nice fit 🤖 !
Check the report carefully, and please buy me a ☕ , or better, a GPU 😉! |
|
You can see at the bottom of the report what the version table looks like ... it's OK but personally I think it could be altered a little to look nicer - anyone else have an opinion? |
|
Ideally I would have three columns: name of the program, version of current, version of reference but don't know how difficult it is with vp (and I don't think it is a table we will be look at a lot) |
The reason I didn't do that is because I also wanted the option to just return the info for one fit only. But I could do two actions, one for just one fit and one (to go in the vp report) with both fits combined. |
|
Ah, makes sense. For me it's ok like this (the only thing I would remove is the index number from the first column I guess). |
|
Yep I agree it's ugly and unnecessary |
Very easy. Have a look at how |
Yes my plan was to do one joint table and one separate table so there are options |
|
As an aside, please delete all "4.0" fits from everywhere. And consider burning the computers where they were installed as an additional safety measure. CC @scarlehoff . |
yeah don't worry I just installed them for this because they had version information |
|
The checks pass now so can we merge this at the code call today? |
|
I thought this was merged already. @voisey @siranipour please approce and merge asap. |
Co-authored-by: Cameron Voisey <32741139+voisey@users.noreply.github.com>
Co-authored-by: siranipour <43517072+siranipour@users.noreply.github.com>
|
Shall I merge? |
|
Yep good to go!! |


Closes #1066.