git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Mr. Sandor Kunyik" <sandor@kane-il.us>
To: git@vger.kernel.org
Subject: Using Git for OpenSCAD and 3D Printing
Date: Tue, 05 Jan 2021 09:57:08 +0000	[thread overview]
Message-ID: <cee9debaf32b69d793d0b8a3e8d4b2c6@kane-il.us> (raw)

Greetings,

If you were to design a new workflow, what key observations would you 
make in regards to OpenSCAD scripts?

As a quick illustration: I have a model with cavities to hold hex bolts 
and nuts. I fine-tuned the model to print on PrinterA, using FilamentA, 
SettingsA. Once in "production" I need to "freeze" all relevant scripts, 
especially when using multi-file structure. If the modules receive 
parameters I need to "remember" those parameters (such as the radius for 
the hex, and the dept of the cavity), and if they use hard-coded values 
I must remember not to change them. Otherwise I cannot repeatedly print 
the same model.

Now imagine this for the entire standard set of hex bolts - each of 
these were fine-tuned, test-printed and verified.
The rationale behind this to guarantee that the models trying to conform 
to a standard (such as ASME B18.3) stay put, while models receiving 
non-standardized sizes such as Nylon 6/6/ (which have bigger hex heads) 
stay separated, and tweaked to work with each supplier.

My question is, should I just "hardcode" everything, set up forks or 
branches for all past scenarios? So far I only have a few dozen models 
and I'm already having a hard time finding models I printed and used in 
the past, to print again. How do I structure all this?

I am a mechanical engineer not a coder, new to all these. Maybe git or 
revision control is not the correct tool for this job?

-- 
Thanks for your time reading,
Sandor

             reply	other threads:[~2021-01-05 10:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-05  9:57 Mr. Sandor Kunyik [this message]
2021-01-11 12:28 ` Using Git for OpenSCAD and 3D Printing Philip Oakley
2021-01-18  6:07   ` Mr. Sandor Kunyik
2021-01-18 23:05     ` Philip Oakley

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=cee9debaf32b69d793d0b8a3e8d4b2c6@kane-il.us \
    --to=sandor@kane-il.us \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).