Fix for UWUW Macro Conflict

[ahnaf-tahmid-chowdhury]

Description:

This PR resolves the following issues in the OpenMC DAGMC interface:

1. Macro Conflict Fix:

   • The UWUW macro was causing conflicts during compilation as it was treated as a numeric constant.
   • To resolve this, the macro UWUW has been replaced with UWUW_HPP to avoid naming conflicts with numeric constants.

   Changes:

   • In CMakeLists.txt, the line:

     target_compile_definitions(libopenmc PRIVATE UWUW)

     has been updated to:

     target_compile_definitions(libopenmc PRIVATE UWUW_HPP)

   • All relevant files that referenced UWUW have been updated accordingly.

2. Const Qualifier Removal:

   • The const qualifier was removed from the function uwuw_assign_material in both the declaration (in dagmc.h) and the definition (in dagmc.cpp).
   • This allows for modifying class member variables within the function, which is necessary for proper material assignment in the DAGMC interface.

[shimwell]

Looks like a file is not being found

/home/runner/work/openmc/openmc/src/dagmc.cpp:15:10: fatal error: uwuw.hpp: No such file or directory
   15 | #include "uwuw.hpp"
      |          ^~~~~~~~~~
compilation terminated.

[pshriwise]

Thanks for this update @ahnaf-tahmid-chowdhury! My only request is that we change the new precompiler value from DAGMC_UWUW to OPENMC_UWUW, using the OPENMC_ prefix as something of a namespace for these precompiler values. We tend to do this with the CAPI functions as well.

[ahnaf-tahmid-chowdhury]

However, some tests are failing with the following error:

ERROR: Material with name/ID 'fuel' not found for volume (cell) 1

It seems that in the recent OpenMC version, all materials must include all the same properties, can't keep anything empty. We need to update the dagmc.h5m file, but I’m not sure how to do that.

[shimwell]

I might be wrong here but that error looks like the openmc materials provided don't include a material with the name 'fuel'.

I don't know why this passed previously but I guess checking the model.materials contain a material with the name fuel would help check and then perhaps the material name can be changed to fuel if it does not exist.

[ahnaf-tahmid-chowdhury]

I don't know why this passed previously but I guess checking the model.materials contain a material with the name fuel would help check and then perhaps the material name can be changed to fuel if it does not exist.

Unfortunately, it was turned off when this was created. I have recently turned it on and found that the related tests are now failing, as it was not updated over time. We should consider turning on all features in our CI to ensure everything is working properly.

[pshriwise]

I don't know why this passed previously but I guess checking the model.materials contain a material with the name fuel would help check and then perhaps the material name can be changed to fuel if it does not exist.

Unfortunately, it was turned off when this was created. I have recently turned it on and found that the related tests are now failing, as it was not updated over time. We should consider turning on all features in our CI to ensure everything is working properly.

I looked into this. I think the .h5m file for this test is fine. The problem originates in #2965 when the read_uwuw_materials() was moved from the initialize method to the uwuw_assign_material method. This was not caught in review or in CI because in CI UWUW was never enabled, as you pointed out @ahnaf-tahmid-chowdhury. Now that UWUW enabled the failure is known, I've pushed a change to this PR moving that call back into the initialize method. The test passes locally for me now. I'll keep an eye on CI here.

[pshriwise]

Looks like that test is passing now. I'll take a look at the changes again shortly.

[pshriwise]

A couple of tweaks for default behavior and one correction to the config file. Ideally we'd our OpenMCCMake.config with some small application that builds on top of the OpenMC installation. @ahnaf-tahmid-chowdhury would you mind making an issue for that task?

[pshriwise]

One small issue with a removed const on a DAGMC method, but then I think this looks good.

[pshriwise]

Thanks for this update @ahnaf-tahmid-chowdhury 👍🏻