-
Notifications
You must be signed in to change notification settings - Fork 64
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Integration of FLUKA with DAGMC in CI #955
Comments
Thanks @ahnaf-tahmid-chowdhury - this wasn't here originally because FLUKA was not always open source. Now that it is, this will be a good additino. |
I found that we need to register to obtain access to the FLUKA binary. Additionally, it's possible to request access to the source code under specific conditions. I have a license for NukeHub, but I believe we'll require a separate license for DagMC for CI integration. Please let me know if you're interested in proceeding with this. |
FLUKA forked a few years ago and there is now a fully open version maintained by CERN, in addition to the managed-access version maintained by others. The purpose of #677 is to change our FLUKA support to work with that version. I am not sure your license to the managed-access version allows you to make it available to others via NukeHub - you should check. |
I think we want to leave the managed-access version behind and rely only on the open source version. |
Yes, I do have the same doubt. Thus, I haven't integrated the FLUKA with the NukeHub. I am planning to ask FLUKA team about this. However, I tried to find an open version of FLUKA but unfortunately didn't find any. The only option I found is through registration. I would be grateful if you could share the link to the open version. |
I think I was wrong - I know there was a forking of the development tree, but I thought one became more open. Perhaps that never happened or has been reversed? I wonder if @makeclean van shed more light on this? |
Description
It has been noticed that DAGMC can use FLUKA as an optional dependency. However, our current CI setup does not include any methods to handle this integration.
Details
Actions Required
The text was updated successfully, but these errors were encountered: