Grid Field Container#
Artisan provides an infrastructure for managing multiple grid fields within a unified container. Users can perform operations directly on these fields, which can then be reused for lattice construction or various geometric operations. Grid field shares the exactly same data structure with the lattice field. Data points with associated field values can be fitted into a field and stored in the container. These stored fields can then be referenced as variables within field-related expressions.
The example .\Test_json\FieldContainer\FitField\FitField.json
demonstrates how to fit a field into the contain variable, perform the mathematical operation, export the field, and re-import the field.
{"Setup":{ "Type" : "Sample",
"Sample": {"Domain" : [[0.0,10.0],[0.0,10.0],[0.0,10.0]], "Shape": "Box"},
"Geomfile": "",
"Rot" : [0.0,0.0,0.0],
"res":[0.1,0.1,0.1],
"Padding": 2,
"onGPU": false,
"memorylimit": 1073741824000
},
"WorkFlow":{
"1": {
"OP_Fit_GridField":{
"inp_ptFieldFile": ".//Test_json//FieldContainer//FitField//cube_points_sdf.csv",
"out_gridFieldFile": "SphereSDF"
}
},
"2":{
"OP_ExprOperation_GridField":{
"expression":"SphereSDF + 10",
"out_gridFieldFile": ".//Test_results//OPdGridField.csv"
}
},
"3":{
"ReadGridField":{
"inp_GridFieldFile": ".//Test_results//OPdGridField.csv",
"Gridfield_ID": "GridField"
}
},
"4":{
"OP_ExprOperation_GridField":{
"expression":"GridField + 1",
"out_gridFieldFile": ".//Test_results//OPdGridField_02.csv"
}
}
},
"PostProcess":{"CombineMeshes": true,
"RemovePartitionMeshFile": false,
"RemoveIsolatedParts": false,
"ExportLazPts": true}
}
Above JSON workflow includes three keywords OP_Fit_GridField
, OP_ExprOperation_GridField
and ReadGridField
. Above workflow does the following operation.
Work item
1
withŌP_Fit_GridField
fits the data points into the grid field.Work item
2
withOP_ExprOperation_GridField
conducts the mathematical operation on the fitted field, and exports the results field into a file.Work item
3
withReadGridField
read the field back to grid field container.Work item
4
withOP_ExprOperation_GridField
conduct another mathematical operation and export the field into a new file.
Please note that above keywords in the workflow were for demonstration purpose. The resultant field in these keywords can be ID for future reference.
The parameters of ŌP_Fit_GridField
is explained below.
Parameter |
Details |
---|---|
|
A file path string to the data points. |
|
A field id that can be referenced in future and this field saves the fitted data, or a file path string to export the fitted field data. |
The parameters of OP_ExprOperation_GridField
is explained below.
Parameter |
Details |
---|---|
|
mathematical expression. The field id can referenced in this expression. The supported mathematical functions are |
|
A fitted field id, or a file path string to export the fitted field data. |
The parameter of ReadGridField
is explained below.
Parameter |
Details |
---|---|
|
A file path string to the grid field file. |
|
A fitted field id for saving the grid field, or a file path string to export the fitted field data. |
Two exported field data files were generated, OPdGridField.csv
and OPdGridField_02.csv
, as shown below on the left and right, respectively. In OPdGridField_02.csv
, the field value was added 1
to the value of the field OPdGridField.png
. This is exactly same as what defined in the workflow.


In Artisan 0.2.14, the grid field container introduces support for defining field-driven TPMS lattices. Future development will focus on extending grid field capabilities to other keywords and applications.