You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If everything goes according to plan, 4.0.9 will bring a lot of changes to the structure of the code -without changing any of the results- and I would like to collect the list of items that we are planning to do (and that needs to be done) to minimize the chance of getting them lost in a sea of smaller PRs.
At the same time, whenever we add some big PR that we should keep track of, it will be added here.
NNPDF 4.0.10
This is the first release towards NNPDF 4.1 and as such this can be considered "NNPDF 4.1 beta". For now we are going to keep 4.0.X in order to keep the tags in the code synchronised with the papers, but it might be changed to 4.1 at a certain point.
Fits for the 4.0 "era" can be reproduced with the tag 4.0.9
Please, don't use this issue to discuss these points (I'm going to lock it indeed, although most of you could still write if you really want :P). If you want to tackle some specific issue, please comment in the relevant PR/issue (or open it if it doesn't exist) or raise it during the code meetings.
The text was updated successfully, but these errors were encountered:
If everything goes according to plan, 4.0.9 will bring a lot of changes to the structure of the code -without changing any of the results- and I would like to collect the list of items that we are planning to do (and that needs to be done) to minimize the chance of getting them lost in a sea of smaller PRs.
At the same time, whenever we add some big PR that we should keep track of, it will be added here.
NNPDF 4.0.10
This is the first release towards NNPDF 4.1 and as such this can be considered "NNPDF 4.1 beta". For now we are going to keep 4.0.X in order to keep the tags in the code synchronised with the papers, but it might be changed to 4.1 at a certain point.
Fits for the 4.0 "era" can be reproduced with the tag 4.0.9
Data and theory implementation #1709
.yaml
files (Make the sqlite theorydb into a folder of yaml files #1997 Provide an unique truth for all theory cards #2028)Performance and logistics
validphys/examples
list are now tested in the CI (Run example runcards in tests #1449)plot_fancy_dataspecs
and chi2 distributions with scale variations #1830, New plotting functions for MHOU #1832, Remove thefivetheories
andseventheories
key and usepoint_prescription
instead. #1847).info
files are read directly with.yaml
Useyaml
for.info
files. #1552Build system and installation
evolven3fit_legacy
andbuildmaster
(Improve the installation ofnnpdf
packages #1773, Simplify development environment installation instructions #1690)evolven3fit
has become the new standard evolution tool${XDG_CONFIG_HOME}/NNPDF/nnprofile.yaml
is now the default location for the NNPDF profile (Implement a python-only installation #1861)redo-regression
in github to autogenerate regression tests (Automate regression updates #1944)pre-commit
has been added to the repository (add .pre-commit-config.yaml #2026)New features
Breaking changes
separate_multiplicative
asFalse
by default #2107evolven3fit
eko.tar
and fastkernel tables in the server #2081, Make EKO into a separate resource #2087)Bugfixes
pseudodata_table
correctly deal with multiple replicas #2034results
to create th uncertainties with pdf errors. #2051Please, don't use this issue to discuss these points (I'm going to lock it indeed, although most of you could still write if you really want :P). If you want to tackle some specific issue, please comment in the relevant PR/issue (or open it if it doesn't exist) or raise it during the code meetings.
The text was updated successfully, but these errors were encountered: