Christopher Sherman

> > > > The fracture is propagating along a partition boundary > > Can it be related to #1000? Odd things do tend to happen along the boundary... I'm...

> > > > > The fracture is propagating along a partition boundary > > > > > > Can it be related to #1000? > > Odd things do...

Also, this time there happened to be a plot-file written on the timestep where the error occured. This shows the fracture aperture, with the domain partition numbers highlighted in the...

> > > @cssherman A couple of observations from your last run.: > > 1. The error is on the application of a kinematic boundary condition, and the error is...

@rrsettgast @joshua-white @af1990 - I've pared down the example problem, modified the xml to output snapshots of the solution matrices, and re-ran the problem. As before, for the serial case,...

@mquanbui - is there a copy of this xml file in the repo?

In this case, my preference would be to hide the table function from the user altogether. Once we are comfortable with one that works in most cases, we could largely...

Also, I'd say that this usage is out of the scope for the function documentation. If an object is going to make modifications to a user-defined table, then the object's...

@klevzoff - my strategy for this has been to use parameters holding absolute paths to handle swapping out meshes, tables, etc. For example: ```xml ``` Also, if we are expecting...

Although, do you mean you would want to do something like this (not manually move the files): ```bash preprocess_xml some_file_with_relative_parameters.xml -c /some/other/path/file_with_fixed_relative_paths.xml ``` That would be pretty simple to implement