Skip to content

Add the option to use one separate network per flavour

Emanuele Roberto Nocera requested to merge n3fit-anetperflavour into master

Created by: scarlehoff

This adds the possibility of using a different network for each flavour.

The code is fully functional, but it is very much work in progress for the following three reasons:

  1. At the moment I've added a dense_per_flavour layer which separates the PDF flavours. Since this is a layer formed by many layer it needs extensive testing to make sure nothing is broken in edge cases.
  2. The construction of the network has become a sea of if clauses I need to clean so it doesn't look like Fortran code from the 80s.

Ant the important one:

  1. This has a very strong synergy with issue #602 (closed). This PR won't close that issue as this only deals with the PDF network itself which depends on the basis only on the output layer and only cares about the size, but it should make my life easier when I tackle issue #602 (closed), at the moment it complicates it very much.

Edit: and of course... 4. Documentation!

Merge request reports