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

Physics question: non-square sticks (b × h) — possible, and at what cost?

Open
  • Is something wrong?
#232 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
javascript
Domain
backend

Research direction

Start by locating the solver, 3D model, sweep engine, file formats, and build document modules named in the issue, then review the challenge PDF or professor's script for the course rules. Work out whether rectangular sections require orientation in 3D and which calculations and formats would change. Done means Physics provides answers to all four questions with a yes, no, or later recommendation; the issue names no files or tests.

Written by the indexing model from the issue text.

Description

P3 physics role: vision status: review
Details

Brian's question: could members use a stick that isn't square (for example 3.18 × 6.35 mm, used on edge or flat), or would that break the system or cost too much to build?

The project's stick is 3.18 mm square (⅛ in), and that stays the default. The UI needs to know whether to plan for a width and a height input or just one size input.

Please answer:

  1. Stiffness and strength. What changes in the solver if a member's section is b × h instead of b × b? In-plane buckling uses the weaker axis I = min(b·h³, h·b³)/12, and the area is b·h. Does the 3D model need the stick's orientation?
  2. Cost. Which modules does it touch (core, core3d, the sweep engine, file formats #149, build documents)? Rough effort?
  3. Risk. Can it be wrong in ways the tests won't catch (for example, a stick turned the wrong way in 3D)?
  4. Course rules. Is a non-square stick even allowed? Only answer from the challenge PDF or the professor's script, or ask Brian.
Acceptance check

A comment from Physics answering 1–4, with a yes, no or later recommendation. Brian decides, and UI then shows either a single "Stick size" input or separate "Stick width" and "Stick height" inputs.

Notes

Raised from the Click-Through notes (Inputs screen: "no input to change the size of the balsa wood profile").

Generated by Claude Code

Dominant language
HTML
Stars
0
Forks
1
Avg merge
1h 15m
Merged PRs (30d)
78

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 briangwalker/TrussExplorer

All issues in briangwalker/TrussExplorer

Similar issues

More Backend & API Design issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.