sales@landfx.com
+1 805-541-1003
Hi All (and Jake),
We have a project that will be constructed in phases. The first phase includes mainline that will not be looped during the first phase. Due to this, as we size it, it will be larger than necessary after the second phase is completed. We will require the mainline to be 2" during the 1st phase. No problem. after taking out the two pieces of pipe that complete the loop on each side of phase 1, LandFX notices only the valves that are being constructed during phase 1. Great. All is good. Oops. Except when we go to size the pipe after connecting the second phase , LandFX sizes the entire loop again. Then the 2" mainline pipe in phase 1 is resized to 1-1/2". But that doesn't work. How would one suggest that we force the phase 1 pipe to maintain it's 2" size which will be necessary during phase 1. This will also reduce the friction calculations for phase 2 since the pipe is really oversized once the loop is completed. Hmmm. Two drawings? both inserted into the paper drawings and xclipped wont work since one can't size the phase 2 properly without connecting it to phase 1. I could force the pipe size to a velocity that would force the 2" pipe for phase 1, but then the phase 2 would be oversized too. . . . . Oh. I don't want to reinvent the wheel. Someone has already done this. Right? @CadMonkey? @Timothy Starkey? @Tom Lang? @Julie Riddle? Rob Streza? @Jake Lott? Jer?
Thanks in advance.
BTW, couldn't attach the JPG of the 75k file that I tried uploading: "The file Phases.jpg which you are attempting to upload is in an unsupported format."
BTW2, after I edited it I fixed a spelling error and tried to resubmit and the system detected my repost as SPAM. That's just messed up.
We have a project that will be constructed in phases. The first phase includes mainline that will not be looped during the first phase. Due to this, as we size it, it will be larger than necessary after the second phase is completed. We will require the mainline to be 2" during the 1st phase. No problem. after taking out the two pieces of pipe that complete the loop on each side of phase 1, LandFX notices only the valves that are being constructed during phase 1. Great. All is good. Oops. Except when we go to size the pipe after connecting the second phase , LandFX sizes the entire loop again. Then the 2" mainline pipe in phase 1 is resized to 1-1/2". But that doesn't work. How would one suggest that we force the phase 1 pipe to maintain it's 2" size which will be necessary during phase 1. This will also reduce the friction calculations for phase 2 since the pipe is really oversized once the loop is completed. Hmmm. Two drawings? both inserted into the paper drawings and xclipped wont work since one can't size the phase 2 properly without connecting it to phase 1. I could force the pipe size to a velocity that would force the 2" pipe for phase 1, but then the phase 2 would be oversized too. . . . . Oh. I don't want to reinvent the wheel. Someone has already done this. Right? @CadMonkey? @Timothy Starkey? @Tom Lang? @Julie Riddle? Rob Streza? @Jake Lott? Jer?
Thanks in advance.
BTW, couldn't attach the JPG of the 75k file that I tried uploading: "The file Phases.jpg which you are attempting to upload is in an unsupported format."
BTW2, after I edited it I fixed a spelling error and tried to resubmit and the system detected my repost as SPAM. That's just messed up.
Accepted Answer
1
Undo
Votes
You keep using examples where the user would *not* want the classes to merge. Try thinking of it differently. Think of it in a case where you *would* want the classes to merge. The aforementioned case where a user wants Poly for the smaller sizes and PVC for the larger sizes, all automatically. Or in Laterals, if a user wants each size pipe to have a different linetype.
So basically, when the system prepares to size, it looks at Class 1, but specifically, the largest size in Class 1. It then looks at Class 2, and if the smallest size of Class 2 is larger than the largest size of Class 1, it treats them all as available sizes in the sizing operation. A user who wants unique linetypes for each size of Lateral would configure 5 or more classes, with the smallest size as Class 1, on up. And the system will combine them all, and treat it as if it was a single a class of pipe, using the full range of sizes.
So the blank is hardly ever needed. But in that rare case, where you happen to have two similar classes, and all the sizes of Class 2 are larger than those of Class 1, it will freely use them. So to prevent this, you could either add some smaller sizes to Class 2, or make Class 2 blank and instead use Class 3.
--J
So basically, when the system prepares to size, it looks at Class 1, but specifically, the largest size in Class 1. It then looks at Class 2, and if the smallest size of Class 2 is larger than the largest size of Class 1, it treats them all as available sizes in the sizing operation. A user who wants unique linetypes for each size of Lateral would configure 5 or more classes, with the smallest size as Class 1, on up. And the system will combine them all, and treat it as if it was a single a class of pipe, using the full range of sizes.
So the blank is hardly ever needed. But in that rare case, where you happen to have two similar classes, and all the sizes of Class 2 are larger than those of Class 1, it will freely use them. So to prevent this, you could either add some smaller sizes to Class 2, or make Class 2 blank and instead use Class 3.
--J
0
Undo
Votes
Still need an answer, but I fixed a spelling error and tried to repost but the system detected my repost as SPAM. That's just messed up. Forrestt, I noticed that the character count has to change. It the misspelled word has the same characters as the correct spelling (ie. "hte and the" or "adn and and" or "It and it"), the gate considers it spam. If one changes the character count, it lets it go through. I just though that you'd like to know that. Maybe there's an adjustment on your side of the curtain Mister Wizard.
Seaweed,
You can do this by skipping a number on the mainline tab in the pipe data dialog box and then only allowing 2" pipe for the phase 1 mainline. By skipping a number, Land F/X won't automatically resize mainline pipe. For example, you can set 1 to be your 2" pipe (image 1) then skip 2 and make sure to make it blank (image 2) and make 3 your mainline pipe for phase 2 (Image 3). Check out the images below.
-Cadmonkey
You can do this by skipping a number on the mainline tab in the pipe data dialog box and then only allowing 2" pipe for the phase 1 mainline. By skipping a number, Land F/X won't automatically resize mainline pipe. For example, you can set 1 to be your 2" pipe (image 1) then skip 2 and make sure to make it blank (image 2) and make 3 your mainline pipe for phase 2 (Image 3). Check out the images below.
-Cadmonkey
Irrigation Project Manager, CLIA
Glasir Design Irrigation Consulting
Glasir Design Irrigation Consulting
0
Undo
Votes
Thanks CadMonkey. 
I’ll use match properties to make the mainline for phase 2 type 3 mainline (and leave type2 blank). That’s a nice secret line of code. I’m glad that it’s documented here now.
I hope to share a beverage with you again my friend. Maybe a game of cornhole too.
I’ll use match properties to make the mainline for phase 2 type 3 mainline (and leave type2 blank). That’s a nice secret line of code. I’m glad that it’s documented here now. I hope to share a beverage with you again my friend. Maybe a game of cornhole too.
0
Undo
Votes
The system is on to you buddy, maybe stop posting so much spam 
I'll take a look at the settings.
Cheers!
I'll take a look at the settings.
Cheers!
Seaweed,
I think I had a similar/related issue years ago and Jerimiah/Jake told me about that "trick". I haven't used in quite a while but I'm fairly certain it will work for you. As for the error that you got while trying to post an image, I got it too. The error was on my side because my jpg file had an extension in all caps (image.JPG). Once I manually changed it to lowercase (image.jpg) the system let me upload my image(s) with no problems.
Definitely look forward to sharing a beverage with you again. And a game of cornhole would be great too. Hopefully we can work out something soon.
-Cadmonkey
I think I had a similar/related issue years ago and Jerimiah/Jake told me about that "trick". I haven't used in quite a while but I'm fairly certain it will work for you. As for the error that you got while trying to post an image, I got it too. The error was on my side because my jpg file had an extension in all caps (image.JPG). Once I manually changed it to lowercase (image.jpg) the system let me upload my image(s) with no problems.
Definitely look forward to sharing a beverage with you again. And a game of cornhole would be great too. Hopefully we can work out something soon.
-Cadmonkey
Irrigation Project Manager, CLIA
Glasir Design Irrigation Consulting
Glasir Design Irrigation Consulting
Would somebody explain why one needs the blank "dummy" main line? Why not just use as many types as you need, set minimum sizes where needed, and label them "Phase 1 Main Line," etc.? I would want all pipe sized and re-sized as I build the system, to make sure I'm within limits.
1
Undo
Votes
Tom,
It allows you to have separate classes. For instance, you could have PVC as class 1, and non-pot as class 3, and the system will never mix them. Or you could have poly as class 1, pvc as class 2, and the system will use poly for the smaller sizes, and pvc for the larger sizes. Then a blank at class 3 will stop it from looking for additional sizes to use.
—J
It allows you to have separate classes. For instance, you could have PVC as class 1, and non-pot as class 3, and the system will never mix them. Or you could have poly as class 1, pvc as class 2, and the system will use poly for the smaller sizes, and pvc for the larger sizes. Then a blank at class 3 will stop it from looking for additional sizes to use.
—J
Thanks Jeremiah, but I'm missing something. What gets mixed, exactly, when you have different pipe types? Doesn't the system "know" what kind of pipe it's sizing? I'll sometimes do two classes of the same pipe material, but one will have a larger minimum size. For example, I'll often put a QC valve at the very end of ML branches, but that short length of pipe does not need to be 2". So I'll use the other class, to get it to 1". The system sizes the pipe correctly. Sometimes I need to include a second material type, such as a poly main line between the meter and the backflow. I've never had issues with incorrect sizing, and have never needed this blank pipe class.
0
Undo
Votes
It will only merge the classes if the smallest of the next size is larger than largest of the previous. As in, class 1 has Poly from 3/4” to 1.5”, then class 2 pvc starts at 2” and goes up.
—J
—J
I guess I don't understand what "merge the classes" means. I don't mean to be obtuse, but none of this makes any sense to me. If Seaweed sets his Phase 1 main line min. size to 2", and uses a second class for phase 2 (without a blank pipe class in between), won't things still size correctly? That's always worked for me.
Accepted Answer
1
Undo
Votes
You keep using examples where the user would *not* want the classes to merge. Try thinking of it differently. Think of it in a case where you *would* want the classes to merge. The aforementioned case where a user wants Poly for the smaller sizes and PVC for the larger sizes, all automatically. Or in Laterals, if a user wants each size pipe to have a different linetype.
So basically, when the system prepares to size, it looks at Class 1, but specifically, the largest size in Class 1. It then looks at Class 2, and if the smallest size of Class 2 is larger than the largest size of Class 1, it treats them all as available sizes in the sizing operation. A user who wants unique linetypes for each size of Lateral would configure 5 or more classes, with the smallest size as Class 1, on up. And the system will combine them all, and treat it as if it was a single a class of pipe, using the full range of sizes.
So the blank is hardly ever needed. But in that rare case, where you happen to have two similar classes, and all the sizes of Class 2 are larger than those of Class 1, it will freely use them. So to prevent this, you could either add some smaller sizes to Class 2, or make Class 2 blank and instead use Class 3.
--J
So basically, when the system prepares to size, it looks at Class 1, but specifically, the largest size in Class 1. It then looks at Class 2, and if the smallest size of Class 2 is larger than the largest size of Class 1, it treats them all as available sizes in the sizing operation. A user who wants unique linetypes for each size of Lateral would configure 5 or more classes, with the smallest size as Class 1, on up. And the system will combine them all, and treat it as if it was a single a class of pipe, using the full range of sizes.
So the blank is hardly ever needed. But in that rare case, where you happen to have two similar classes, and all the sizes of Class 2 are larger than those of Class 1, it will freely use them. So to prevent this, you could either add some smaller sizes to Class 2, or make Class 2 blank and instead use Class 3.
--J
- Page :
- 1
There are no replies made for this post yet.
Be one of the first to reply to this post!
Be one of the first to reply to this post!
