Meshing in parts of large models

[ebknudsen]

Meshing a large model can be quite cumbersome. It would therefore be very nice to be able to split the geometry into several different parts.

• It would be reasonable to ask a user to guarantee that the various models do not overlap. If they do they wont work.
• If they do overlap, it would in theory be possible to define a priority that would solve this, but this requires the underlying transport algorithm to handle this. different routes spring to mind:
  1. Either we define a merging algorithm in the assembly class that can merge two assemblies. This would perhaps run into problems with respect to the whole data_directory notion. As long as it is there, it should be possible.
  2. The other option is to implement this inside the DAGMC-layer that one can have more than one model within a universe. Not clear how to do that - but if the import-routines could be made aware that we should in fact not stop at one but also import yet another model - this could end up being practicable

[ebknudsen]

The algorithm suggested by 1 has now been implemented by 04fac02dc5.

a function merge2h5m is defined in assembly.py that may be called

merge2h5m([A,B,C,D],'output.h5m')

where A,B,C, and D are assemblies that have previously been meshed. A drawback is that the assemblies have to be meshed on the fly, i.e. there is no import h5m-functionality yet.

The very good part is that it simplifies the turnaround time when debugging problematic models.

[ebknudsen]

closing this. Will reopen more specific issues for other projects