nikosarcevic/hep-astro-cosmo

HEP/Astroparticle/Astrophysics/Cosmology open source packages. Community effort. Physics people, unite!

hep-astro-cosmo's Issues

two packages: where to include

I am not a HEP person so I am struggling with where to include these two resources - suggestions welcome

• https://www.xfitter.org/xFitter/ (I guess in the Fitters section?)
• https://lhapdf.hepforge.org (otters as well or something else?)

ASPIC: Accurate Slow-roll Predictions for Inflationary Cosmology

Please add ASPIC into your list, I think you don't have it yet in your list.
http://cp3.irmp.ucl.ac.be/~ringeval/aspic.html

galaxy mocklist

thanks to Cora

Keywords

It is probably convenient to include keywords for each software package beyond the rough breakdown in the readme file.

Phil Bull's code - ADD

http://philbull.com/#code

add this cosmo codes notebook

not software per se but super useful

https://gitlab.com/dhirajhazra/simple-codes-in-cosmology

check if nbodykit is already included

https://nbodykit.readthedocs.io/en/latest/index.html

check some codes in these gh repos

• https://github.com/nebblu
• https://github.com/wll745881210?tab=repositories
• https://github.com/martinjameswhite
• https://github.com/sfschen
• https://github.com/modichirag
• https://github.com/eelregit
• https://github.com/bccp
• https://github.com/cajohare
• https://github.com/temken
• https://github.com/JelleAalbers
• https://github.com/anikhalder
• https://github.com/OliverFHD
• https://github.com/dr-guangtou/taotie/blob/master/astro/topics/simulations.md
• https://github.com/lgarrison

Add NNPDF fitting code

We (meaning the NNPDF collaboration) recently open sourced our PDF fitting code:

https://github.com/NNPDF/nnpdf

The documentation is in: https://docs.nnpdf.science/

As to where to classify it, I guess between xfitter and LHAPDF is the obvious place.

Some other codes (shameless plug):

• PDFFlow: https://github.com/N3PDF/pdfflow, basically a clone of LHAPDF that uses TensorFlow and thus can be used to target GPUs
• MadFlow: https://github.com/N3PDF/madflow an automatic event generator using TensorFlow and which can be used to target GPUs.

I can open a PR with all that if it is easier that way.

simulations cleanup

definitely need to rethink how t restructure the cosmo sims category. plan of action: first add all the code then see how to organize.

Some neutrino code

I have been collecting a list of neutrino related code here: https://peterdenton.github.io/Code/index.html.

Structure

rethink how to structure this. majority of links are HEP so we need astro and cosmo stuff. so maybe shove everything under HEP you have so far. to do: gather more astro(particle) and cosmo links. ask around. this is more of a note to myself and whoever wants to join. excuse the language.

Cleanup of branches

Currently there's a number of branches that are listed as stale. Are these still relevant? Maybe these should be merged (if not already) and cleaned up/deleted.

add CAMELS dataset

https://camels-multifield-dataset.readthedocs.io/en/latest/

https://arxiv.org/pdf/2109.10915.pdf

Where to include xmds

http://www.xmds.org

package to use to solve ODEs, PDEs and SDEs. Used by people who work on BECs. Not sure if technically cosmology but some cosmologists use it.

Question is - should this be in the Cosmo section or not?
Thoughts?

add nbody kit

https://nbodykit.readthedocs.io/en/latest/

wrong url for Monte Python

Hi, thanks for the nice work!
I just noticed that for Monte Python you have put the obsolete GitHub URL of MontePython (until 2017 and v2.2): https://github.com/baudren/montepython_public/wiki
The GitHub URL of MontePython (since 2018 and v3.0) is:
https://github.com/brinckmann/montepython_public
Please do the substitution. The old URL is not maintained since 2017.
Julien Lesgourgues

add Quijote

https://quijote-simulations.readthedocs.io/en/latest/

add PLUTO code

http://plutocode.ph.unito.it

Decide approval process

Somewhat related to #9 , we should agree an approval process about how packages that meet the criteria we defined are added to the list, and then also add text to the list telling users how to submit their packages to the list. To me, in the long run, it makes to do 1 Pull request/package add, then we can set up discussions on that PR if need be to refine the package listing up to whatever standards we decide.

Any thoughts?

Collaboration with existing repositories

Just want to point out that we should be careful with the scope of this listing and also manage collaboration with other existing repositories. e.g. I would link ASCL for as many astro tools as possible and send any astro tools nominations there. Same goes for neutrino codes and send those to Peter Denton who's managing it.

What do the others think?

To include

A list of TO-INCLUDEs

• go thru this paper https://arxiv.org/abs/1905.13189
• check inspire page https://inspirehep.net/experiments?sort=mostrecent&size=25&page=1&q=&classification=Non-experimental
• check https://ascl.net/home/getwp/958
• decide where to list these (copied from issue #13 ) So, here there are a compilation of tools for the Standard Model Effective Field Theory (SMEFT) https://inspirehep.net/literature/1760709 and at https://renatofonseca.net/ one can find 3 mathematica packages (GroupMath, Sym2Int and Susyno) for model building and supersymmetric RGEs.)
• rename FeynFamily to Symbolic manipulation tools (mathematica) and add GroupMath, Sym2Int and Susyno there. These are all symbolic manipulators, not numerical tools. I think so far they all belong to hep than cosmo category.
• There are also interesting developments on pyhep (https://hepsoftwarefoundation.org/workinggroups/pyhep.html…) and
  @tensorflow
  based fitting tools (https://github.com/zfit/zfit). Last but not list NN parameterization of full likelihood (https://github.com/riccardotorre/DNNLikelihood…)
• https://github.com/fastmachinelearning
• https://hepfit.roma1.infn.it

add gevolution code

https://github.com/gevolution-code

SMEFT tools and others

I just created my github account so I don't know exactly how to add things or how anything works actually :). So, here there are a compilation of tools for the Standard Model Effective Field Theory (SMEFT) https://inspirehep.net/literature/1760709 and at https://renatofonseca.net/ one can find 3 mathematica packages (GroupMath, Sym2Int and Susyno) for model building and supersymmetric RGEs.

Cheers

Criteria for including a code

I guess we should consider what criteria we want to use for including a code in this list. My instinct is that we should be very permissive/inclusive. But we should probably only include codes which are in some sense 'tools' (i.e. which have the possibility of being re-used by other people), rather than codes which are very specific in scope (e.g. codes/repos which reproduce a particular result/paper, rather than providing more general functionality). Thoughts?

Include flavio / smelli in HEP global fitters

flavio - https://flav-io.github.io/
smelli - https://smelli.github.io/

I will turn this into a pull request later when I have time

add camels

https://camels.readthedocs.io/en/latest/

Badges for astropy affiliation etc

In astronomy we have this idea of astropy affiliated packages (https://www.astropy.org/affiliated/), which are packages that use the 'astropy' ecosystem and meet certain standards about code development etc, agnpy (which I just added to the readme.md) is an example of one. It might be worth especially marking those somehow. Is there an equivalent setup in HEP?

Suggest to add references

One common issue with citing code in papers is that authors of code do not always provide clear instructions on how to cite the software. Sometimes it's a zenodo doi pointing to a webpage or a github repo, sometimes a paper, sometimes the user guide, sometimes a proceedings. I suggest we try to systematically list the recommended citation for each software.

Check stuff from Andy

https://www.ppe.gla.ac.uk/~abuckley/

check if ReACT is on the list

https://github.com/nebblu/ReACT