This is the dirtiest (but most minimal) implementation possible. The executable is generated in the apfelcomb/src folder and the user has to include this location to the PATH environmental variable. Perhaps explicit mention to this should be included in the documentation. Better installation locations can be considered, however I'm not sure if this is worth doing, in view of the fact that apfelcomb is going to be replaced.
This PR addresses https://github.com/NNPDF/nnpdf/issues/1540 reinstates
FKmerge2
asfkmerge2
, which was inadvertently deleted here https://github.com/NNPDF/nnpdf/commit/bed162e4a3ebc2e343f6289fc677863c552a6dd8This is the dirtiest (but most minimal) implementation possible. The executable is generated in the
apfelcomb/src
folder and the user has to include this location to thePATH
environmental variable. Perhaps explicit mention to this should be included in the documentation. Better installation locations can be considered, however I'm not sure if this is worth doing, in view of the fact that apfelcomb is going to be replaced.cc @J-M-Moore