# Question on the results from examples/3d/hex8 step06-08

**URL:** <https://community.geodynamics.org/t/question-on-the-results-from-examples-3d-hex8-step06-08/1422>\
**Category:** PyLith\
**Created:** [September 2, 2020, 10:16pm UTC](https://community.geodynamics.org/t/question-on-the-results-from-examples-3d-hex8-step06-08/1422 "2020-09-02T22:16:28Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![gcheng6](https://avatars.discourse-cdn.com/v4/letter/g/65b543/32.png) [@gcheng6](https://community.geodynamics.org/u/gcheng6)\
**Post date:** [September 2, 2020, 10:16pm UTC](https://community.geodynamics.org/t/question-on-the-results-from-examples-3d-hex8-step06-08/1422/1 "2020-09-02T22:16:28Z")

</div>

Hi,

I ran the steps 6-8 in examples/3d/hex8 and everything works fine, no error messages show up. However, when I try to view the stepXX-fault\_info.xmf file in Paraview, it seems that the results for final\_slip\_creep and final\_slip\_one, as well as slip\_time\_creep and slip\_time\_one, are inverted. I did not change the original .cfg files, so I wonder what could cause this?

Thanks!

---

<div class="post-metadata">

**Author:** ![baagaard](https://yyz2.discourse-cdn.com/flex036/user_avatar/community.geodynamics.org/baagaard/32/615_2.png) [@baagaard](https://community.geodynamics.org/u/baagaard)\
**Post date:** [September 3, 2020, 8:35pm UTC](https://community.geodynamics.org/t/question-on-the-results-from-examples-3d-hex8-step06-08/1422/2 "2020-09-03T20:35:12Z")

</div>

You are correct! Thanks for reporting this.

I am seeing that the field label `final_slip_creep` is really `final_slip_one` and vice versa. The Xdmf is correctly pointing to the corresponding field in the HDF5 file, so the error is occurring in getting the info fields within PyLith. The likely issue is that we are either using a buffer with stale data or we have a mismatch between the earthquake rupture data and the name of the earthquake rupture. My guess is that it is the latter. I don’t see an obvious mistake in taking a quick look at the code.

We are getting close to finishing the v3.0 release, so we may decide to make note of this bug but not fix it. The v3.0 release is almost a complete rewrite of PyLith and the way we store this type of information and write it out is completely different, so this same bug doesn’t exist in v3.0.

See [Fault info fields for ruptures swapped in HDF5 output](https://github.com/geodynamics/pylith/issues/206) in the GitHub PyLith repo issues to track any further discussion or information (including potential resolution) about this bug.