Combine list labeling and support script parametrization to keep identifiable test parts associable with variations of support shapes
Overview
In the course of this tutorial, several independent functions across
Netfabb come to use to demonstrate preparation and execution of giving individual parts their own similar but individualized supports.
It is not strictly necessary that all involved parts are actually clones of the same original part, just with modified names. Parts that differ too much to be supported with the same support script could lead to unpredictable and unusable results.
-
Modify renaming rules for labeling
- By default, the renaming template for labeling adds a
(labeled) suffix.
- To use parameter matching, the matched text must be completely at the trailing end of the part names. The default suffix would interfere with that.
- Additionally, list labeling inserts the text of the
Value field from the renaming list before the suffix, but without a space character so as to not introduce double spaces. While this does not interfere with name matching, the name added without a space may not meet your requirements.
-
Text from list labeling
- A CSV file is manually prepared with individual names. This serves as a stand-in for any practical source of lists.
- The CSV file is imported to populate the naming list for the labeling.
- This list is then used to generate part clones with known names.
-
Parametrized support script
- A support script is created and configured to use a list of parameter variation.
- The CSV file created earlier is reused to populate the parametrization table.
- The table is completed with the parameters to variate and the adjusted values per parameter.
-
Supporting multiple individual parts in the buildroom in parallel
- The support editor works on a single part at a time only.
- Supporting multiple parts at a time requires a support script to already exist.
- A support script is most conveniently created using the support editor as it provides tools and functions designed to assist with this task. Technically, a support script could also be generated externally and made available for the next launch of
Netfabb, but this is out of scope of this tutorial.