How about storing the git hash and the output of git diff? If you are on a public branch that might be a good compromise and a valid reference no?
Matthieu On Apr 27, 2016, at 8:34 AM, Vincent, Peter E <[email protected]<mailto:[email protected]>> wrote: Hi Piotr, Thanks for the suggestion. This is something we have discussed quite a lot. One issue is that you can never be sure that the version that is run is exactly the same as a release. The user may have made some ‘small tweaks’ (or even bigger changes), and the code would still tag results as being from e.g. release v1.4.0, when in fact they were not, which has the potential to cause significant confusion and erroneous comparisons. We have also considered embedding the entire source code in every solution dump etc. such that solution files could at some level re-generate themselves, and this is something we may add going forwards. Although even that is not fool proof since you may have a difference dependency stack in the future. Cheers Peter Dr Peter Vincent MSci ARCS DIC PhD Senior Lecturer and EPSRC Early Career Fellow Department of Aeronautics Imperial College London South Kensington London SW7 2AZ email: [email protected]<mailto:[email protected]> web: www.imperial.ac.uk/aeronautics/research/vincentlab/<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.imperial.ac.uk_aeronautics_research_vincentlab_&d=CwMFaQ&c=IV_clAzoPDE253xZdHuilRgztyh_RiV3wUrLrDQYWSI&r=T_yKAg1nAqY6Ev-ueYwGlg&m=0jsmVhby6AKCjWvRtQq0hjUzOPytIzN5uAZpIhwAntw&s=2aV67BP0jH32KNpjByiNYkWMmqIKFyInnBxy34ECHO4&e=> twitter: @Vincent_Lab<https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_-23-21_Vincent-5FLab&d=CwMFaQ&c=IV_clAzoPDE253xZdHuilRgztyh_RiV3wUrLrDQYWSI&r=T_yKAg1nAqY6Ev-ueYwGlg&m=0jsmVhby6AKCjWvRtQq0hjUzOPytIzN5uAZpIhwAntw&s=cJ3xxVHh6deentiN4UixeXO2qUYup8Yg6M55eu0MpEA&e=> On 27 Apr 2016, at 13:24, Piotr Prusiński <[email protected]<mailto:[email protected]>> wrote: Hello, Just a silly idea, but I believe there is one thing that could be useful at some point of the development. I mean, maybe it would be wise to add an information about the pyfr version somewhere in the output of the simulation, that could help to either track and compare the scalability version-to-version or any other improvements in the code later on. This could be placed i.e. in the header of residual file or in some separate summary file that could contain also some performance benchmarking info. What do you think? Best regards Piotr Prusiński, M.Sc. Eng. --- Senior CFD Specialist CFD Analysis Group (UZ3) National Centre for Nuclear Research (NCBJ) A. Sołtana 7, PL-05400 Otwock-Świerk phone: +48.222731126 e-mail: [email protected]<mailto:[email protected]> -- You received this message because you are subscribed to the Google Groups "PyFR Mailing List" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]<mailto:[email protected]>. To post to this group, send email to [email protected]<mailto:[email protected]>. Visit this group at https://groups.google.com/group/pyfrmailinglist<https://urldefense.proofpoint.com/v2/url?u=https-3A__groups.google.com_group_pyfrmailinglist&d=CwMFaQ&c=IV_clAzoPDE253xZdHuilRgztyh_RiV3wUrLrDQYWSI&r=T_yKAg1nAqY6Ev-ueYwGlg&m=0jsmVhby6AKCjWvRtQq0hjUzOPytIzN5uAZpIhwAntw&s=iBfusvVLMr1WHKeNoaZSOgaQXoYTS7m3lVFDzbed90c&e=>. For more options, visit https://groups.google.com/d/optout<https://urldefense.proofpoint.com/v2/url?u=https-3A__groups.google.com_d_optout&d=CwMFaQ&c=IV_clAzoPDE253xZdHuilRgztyh_RiV3wUrLrDQYWSI&r=T_yKAg1nAqY6Ev-ueYwGlg&m=0jsmVhby6AKCjWvRtQq0hjUzOPytIzN5uAZpIhwAntw&s=4fbT2milC54EWguXh6_24NONFnGWqwNvaaup2DLNHQI&e=>. -- You received this message because you are subscribed to the Google Groups "PyFR Mailing List" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]<mailto:[email protected]>. To post to this group, send email to [email protected]<mailto:[email protected]>. Visit this group at https://groups.google.com/group/pyfrmailinglist<https://urldefense.proofpoint.com/v2/url?u=https-3A__groups.google.com_group_pyfrmailinglist&d=CwMFaQ&c=IV_clAzoPDE253xZdHuilRgztyh_RiV3wUrLrDQYWSI&r=T_yKAg1nAqY6Ev-ueYwGlg&m=0jsmVhby6AKCjWvRtQq0hjUzOPytIzN5uAZpIhwAntw&s=iBfusvVLMr1WHKeNoaZSOgaQXoYTS7m3lVFDzbed90c&e=>. For more options, visit https://groups.google.com/d/optout<https://urldefense.proofpoint.com/v2/url?u=https-3A__groups.google.com_d_optout&d=CwMFaQ&c=IV_clAzoPDE253xZdHuilRgztyh_RiV3wUrLrDQYWSI&r=T_yKAg1nAqY6Ev-ueYwGlg&m=0jsmVhby6AKCjWvRtQq0hjUzOPytIzN5uAZpIhwAntw&s=4fbT2milC54EWguXh6_24NONFnGWqwNvaaup2DLNHQI&e=>. -- You received this message because you are subscribed to the Google Groups "PyFR Mailing List" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send an email to [email protected]. Visit this group at https://groups.google.com/group/pyfrmailinglist. For more options, visit https://groups.google.com/d/optout.
