I did some initial exploring of what will be needed to use pipeline as the data source for pipes and fittings.
Pipeline will need to add SDR and/or schedule as an input so that it can design a pipe based on ID (the hydraulic requirement)
Currently isn't possible to select a pipe based on ID. I get an error (can not subtract number and ValueWithUnits.
I'd propose the following for the variable names
outerDiameter - OD
innerDiameter - ID (this could be confusing with id used for the part number...)
nominalDiameter - ND
length - L
maximum length (this field seems confusing because it isn't a maximum, it is just the length of that particular part number)
Monroe created functions that get pipe and coupling dimension information using the fitting services. The functions add SDR as an input and calculate the pipe ID based on the SDR.
Use queryPipe and queryFitting to obtain pipe info from pipeline. Implement this first in the Drain Pipe Stub Smart Component
I did some initial exploring of what will be needed to use pipeline as the data source for pipes and fittings. Pipeline will need to add SDR and/or schedule as an input so that it can design a pipe based on ID (the hydraulic requirement) Currently isn't possible to select a pipe based on ID. I get an error (can not subtract number and ValueWithUnits. I'd propose the following for the variable names outerDiameter - OD innerDiameter - ID (this could be confusing with id used for the part number...) nominalDiameter - ND length - L maximum length (this field seems confusing because it isn't a maximum, it is just the length of that particular part number)
Monroe created functions that get pipe and coupling dimension information using the fitting services. The functions add SDR as an input and calculate the pipe ID based on the SDR.