Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Nrmlwr fix, fixed issues seen with USRBDX #103

Closed
wants to merge 68 commits into from
Closed

Conversation

makeclean
Copy link
Contributor

The original implementation was incorrect, the fixes here rectify the problems with nrmlwr and solve #100.

Now, this may need some git magic to put right, I believe I have committed my change in the correct place.

I don't believe next_surf was being properly updated and restored based on g1wr, now the logic is

  • upon entry set next_surf -> prev_surf (set on exit of the g1wr)
  • if prop_step takes us across the boundary, next_step set by ray_fire
  • if it does not we reset next_surf to be prev surf (as it was on entry)
  • finally update prev_surf = next_surf for use in next entry

Furthermore, in nrmlwr, Fluka treats senses in the opposite fashion to mcnp

  • If sense == 1 i.e. foward of the cell, then we need to reverse the direction of the normal, since this is what fluka expects.

Testing seen in #100 show the issue is rectified.

makeclean and others added 30 commits April 10, 2013 12:27
…filename, which then copies file to dagmc.h5m
…udagwork

Conflicts:
	FluDAG/src/cpp/fluka_funcs.cpp
Julie C. Zachman and others added 23 commits May 6, 2013 10:26
… earch

through all volumes to find volume xyz is in
I am performing my first merge, smoke me a kipper, Ill be back for breakfast.
@gonuke
Copy link
Member

gonuke commented Jun 21, 2013

Let's review the git part of this on Monday when I'm in the office.

@makeclean
Copy link
Contributor Author

This shouldnt be into master, Ignore this!!

@gonuke
Copy link
Member

gonuke commented Jun 21, 2013

Yes - just realized that too - if a pull request against fludagwork then I think it'll look much better.

@gonuke gonuke closed this Jun 21, 2013
ljacobson64 pushed a commit to ljacobson64/DAGMC that referenced this pull request Jun 5, 2017
PR svalinn#103: Adding the explicitly created skin entities to the passed
non-null meshset.

The existing skinner functionality adds the explicitly created skin
entities only to the root set without adding the same to any passed
meshset. This behaviour is changed in this PR. Now, if a non-null
meshset is passed and the skin entities are created, then the new
entities would be added to the meshset as well.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants