Feature/andrembcosta/multi resolution solver
Creating PR for Multi-Resolution solver
@andrembcosta I think you deleted the integratedTests directory...
Should I re-create it? I think I was having some problems authenticating in the integratedTests repository.
Should I re-create it? I think I was having some problems authenticating in the integratedTests repository.
I think I have fixed it but if you have permissions problems let's solver them. Deleting it seems to create quite a few headaches when merging.
Ok, I will try to pull here and see exactly what the error is.
fracturedElements should not be empty anymore. I will fix the external set later.
@rrsettgast, @CusiniM
what about merging this simplified version where the meshes of base and patch are identical?
To do:
- there seems to be a type issue with a 2D array in GPU builds; - FIXED
- verify correct path to apply BCs with multiple bodies;
- add MR integratedTest and rebaseline PF tests because of change in fieldName.
Issue with objectPath in the inputFile.
In the MR solver, we need to specify the displacement BCs to the base problem. Prior to this most recent develop merge, the following FieldSpecification was doing that:
<FieldSpecification
name="ypos"
objectPath="base/Level0/nodeManager"
fieldName="totalDisplacement"
component="1"
scale="1.0e-7"
functionName="f_b"
setNames="{ ypos }"/>
now, it seems that it is not finding this objectPath. What worked was to use objectPath="nodeManager", which apparently defaults to MeshBody(0) and gives the right answer.