See also the Slicer Recommendations printing information.
Instructions are for Windows, however Linux and OSX are esssentially the same but scripts to automate batch building are not provided.
Copy your calibration files and any .json parameter adjustment files you have created to another directory before update to a newer version of PELA-blocks, you might overwrite your calibration customizations.
cd PELA-blocks
cp material.scad ..
cp *.json ..
This saves space on your computer, bandwidth and time. Only the latest version of generated STL and PNG images is kept locally.
git config core.sparcecheckout true
OpenSCAD exports large text files which 2x larger than binary STL. They may also contain mistakes (non-manifold, etc). Usually your slicer can handle this just fine.
Cleaning and compressing the STL before slicing is optional but may help if you Slicer complains about the file. A quick solution is to load and re-save the file generated by OpenSCAD in Windows 3D Builder (Open the file, Click YES
to fix, then CTRL S
to save over the original file), Meshlab or Meshmixer.
It is also possible to setup a batch process to clean and re-save multiple .STL
files using Meshlab. We used to do this but simplified it away as it adds little value. If you know of a better batch tool for cleaning files, please let us know.
To keep the files size down in the repository when many .stl
and .png
files start to clutter it, occational cleanup is in the following script which runs on both Linux and Windows.
./gitcleanup.ps1