Stress tensor view: principal arrows and their labels are hidden by the atoms

Open
#1,021 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
c

Research direction

This is a design decision, not a ready patch: the issue lists three options and asks for mock-ups first. Start by reading #1015 for how the principal-stress arrows and their labels are drawn, then reproduce on the qe-tension test cell (4-atom fcc, CPK spheres) with the Show in viewer option. Done means a maintainer has picked one option and a mock-up or change shows labels readable with atoms not hiding the arrows.

Written by the indexing model from the issue text.

Description

enhancement

The principal-stress arrows (#1015) are drawn through the cell centre and pass through the atoms of a filled cell; their labels ("+0.484 GPa (+4.840 kbar)") are drawn at the arrow tips and collide with atoms, and the label of the axis pointing at the viewer is unreadable. Seen on the qe-tension test cell (4-atom fcc, hydrostatic tension), CPK spheres.

Options to decide (mock-ups first):

  • draw the arrows on top of the atoms (no depth test, or a transparent overlay layer), or offset them outside the cell;
  • one label per axis outside the cell, or the values only in the panel table with the arrows unlabelled;
  • show arrows only when Show in viewer is ticked and dim the atoms meanwhile.
Dominant language
C
Stars
10
Forks
8
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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 FriendsofECCE/ECCE

All issues in FriendsofECCE/ECCE

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.