Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Slice.to_global drops upper-face nodes of meshes without a neighbour

Open
#121 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
70/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
python
Domain
data

Research direction

Start in slcf/slice.py at Slice.to_global() and read the “We ignore border points ...” step, then look for tests covering this method. Reproduce the reported L-shaped, 8-mesh case and check that upper-face nodes are retained from their own mesh when no neighbour covers them; done means those exterior-wall values are no longer NaN.

Written by the indexing model from the issue text.

Description

Slice.to_global() (1.11.7 and 1.12.1, slcf/slice.py, the "We ignore border points ..." step) drops the last node row of every mesh on its upper x/y face and adds it back only at the global maximum, assuming a neighbouring mesh supplies those nodes. Where no neighbour exists, on a domain that does not fill its bounding box (e.g. an L-shaped corridor), the nodes stay NaN although FDS wrote them.

Example: an L-shaped corridor of 8 meshes at 0.25 m, node-based SLCF at z = 2.0 m. 208 nodes on the exterior walls are NaN for this reason. All of them lie on upper faces of meshes below the global maximum; none is strictly inside a mesh. The values are present in each mesh's subslice data.

Expected: an upper-face node is taken from its own mesh when no neighbouring mesh covers it.

Found through fdsvismap, which reads slices with to_global().

Dominant language
Python
Stars
75
Forks
28
Avg merge
2m
Merged PRs (30d)
2

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from FireDynamics/fdsreader

All issues in FireDynamics/fdsreader

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.