Alternative to nested case structures??

[RoboNuC4]

Hello, 

I am currenly making a simulation of using a chromatography column using LabVIEW NXG. I haven't come far yet, but I already see that I have too many nested case structures. 

Some of the logic I have in there is: 

Has the user pressed "condition"-button?

       If True: Is the column empty?

               If True: Is the selected conditioning volume less than or equal to 0? (invalid number)

                         If False: Is the conditioning volume less than or equal to 10? (maximum volume this specific column can hold)

                                      If True: valves open and conditioning starts. 

The question is: Is there a cleaner way to do this?

Thank you in advance!

[RoboNuC4]

Hello, 

I am currenly making a simulation of using a chromatography column using LabVIEW NXG. I haven't come far yet, but I already see that I have too many nested case structures. 

Some of the logic I have in there is: 

Has the user pressed "condition"-button?

       If True: Is the column empty?

               If True: Is the selected conditioning volume less than or equal to 0? (invalid number)

                         If False: Is the conditioning volume less than or equal to 10? (maximum volume this specific column can hold)

                                      If True: valves open and conditioning starts. 

The question is: Is there a cleaner way to do this?

Thank you in advance!

[RoboNuC4]

Hello, 

I am currenly making a simulation of using a chromatography column using LabVIEW NXG. I haven't come far yet, but I already see that I have too many nested case structures. 

Some of the logic I have in there is: 

Has the user pressed "condition"-button?

       If True: Is the column empty?

               If True: Is the selected conditioning volume less than or equal to 0? (invalid number)

                         If False: Is the conditioning volume less than or equal to 10? (maximum volume this specific column can hold)

                                      If True: valves open and conditioning starts. 

The question is: Is there a cleaner way to do this?

Thank you in advance!

[RoboNuC4]

Hello, 

I am currenly making a simulation of using a chromatography column using LabVIEW NXG. I haven't come far yet, but I already see that I have too many nested case structures. 

Some of the logic I have in there is: 

Has the user pressed "condition"-button?

       If True: Is the column empty?

               If True: Is the selected conditioning volume less than or equal to 0? (invalid number)

                         If False: Is the conditioning volume less than or equal to 10? (maximum volume this specific column can hold)

                                      If True: valves open and conditioning starts. 

The question is: Is there a cleaner way to do this?

Thank you in advance!

[RoboNuC4]

Hello, 

I am currenly making a simulation of using a chromatography column using LabVIEW NXG. I haven't come far yet, but I already see that I have too many nested case structures. 

Some of the logic I have in there is: 

Has the user pressed "condition"-button?

       If True: Is the column empty?

               If True: Is the selected conditioning volume less than or equal to 0? (invalid number)

                         If False: Is the conditioning volume less than or equal to 10? (maximum volume this specific column can hold)

                                      If True: valves open and conditioning starts. 

The question is: Is there a cleaner way to do this?

Thank you in advance!

[RoboNuC4]

Hello, 

I am currenly making a simulation of using a chromatography column using LabVIEW NXG. I haven't come far yet, but I already see that I have too many nested case structures. 

Some of the logic I have in there is: 

Has the user pressed "condition"-button?

       If True: Is the column empty?

               If True: Is the selected conditioning volume less than or equal to 0? (invalid number)

                         If False: Is the conditioning volume less than or equal to 10? (maximum volume this specific column can hold)

                                      If True: valves open and conditioning starts. 

The question is: Is there a cleaner way to do this?

Thank you in advance!

[RoboNuC4]

Hello, 

I am currenly making a simulation of using a chromatography column using LabVIEW NXG. I haven't come far yet, but I already see that I have too many nested case structures. 

Some of the logic I have in there is: 

Has the user pressed "condition"-button?

       If True: Is the column empty?

               If True: Is the selected conditioning volume less than or equal to 0? (invalid number)

                         If False: Is the conditioning volume less than or equal to 10? (maximum volume this specific column can hold)

                                      If True: valves open and conditioning starts. 

The question is: Is there a cleaner way to do this?

Thank you in advance!

[RoboNuC4]

Hello, 

I am currenly making a simulation of using a chromatography column using LabVIEW NXG. I haven't come far yet, but I already see that I have too many nested case structures. 

Some of the logic I have in there is: 

Has the user pressed "condition"-button?

       If True: Is the column empty?

               If True: Is the selected conditioning volume less than or equal to 0? (invalid number)

                         If False: Is the conditioning volume less than or equal to 10? (maximum volume this specific column can hold)

                                      If True: valves open and conditioning starts. 

The question is: Is there a cleaner way to do this?

Thank you in advance!

[Kyle97330]

Stop using "type cast" and start using "coerce to type".

"Type cast" could be thought of as being a brute force conversion, it just tells LabVIEW to do its best to change the raw bit data of one data type to another.

"Coerce to type" is a much more intelligent conversion, which is what you need in this case.

[Kyle97330]

Stop using "type cast" and start using "coerce to type".

"Type cast" could be thought of as being a brute force conversion, it just tells LabVIEW to do its best to change the raw bit data of one data type to another.

"Coerce to type" is a much more intelligent conversion, which is what you need in this case.

[Kyle97330]

Stop using "type cast" and start using "coerce to type".

"Type cast" could be thought of as being a brute force conversion, it just tells LabVIEW to do its best to change the raw bit data of one data type to another.

"Coerce to type" is a much more intelligent conversion, which is what you need in this case.

[Kyle97330]

Stop using "type cast" and start using "coerce to type".

"Type cast" could be thought of as being a brute force conversion, it just tells LabVIEW to do its best to change the raw bit data of one data type to another.

"Coerce to type" is a much more intelligent conversion, which is what you need in this case.

[Kyle97330]

Stop using "type cast" and start using "coerce to type".

"Type cast" could be thought of as being a brute force conversion, it just tells LabVIEW to do its best to change the raw bit data of one data type to another.

"Coerce to type" is a much more intelligent conversion, which is what you need in this case.

[Kyle97330]

Stop using "type cast" and start using "coerce to type".

"Type cast" could be thought of as being a brute force conversion, it just tells LabVIEW to do its best to change the raw bit data of one data type to another.

"Coerce to type" is a much more intelligent conversion, which is what you need in this case.

[Kyle97330]

Stop using "type cast" and start using "coerce to type".

"Type cast" could be thought of as being a brute force conversion, it just tells LabVIEW to do its best to change the raw bit data of one data type to another.

"Coerce to type" is a much more intelligent conversion, which is what you need in this case.

[Kyle97330]

Stop using "type cast" and start using "coerce to type".

"Type cast" could be thought of as being a brute force conversion, it just tells LabVIEW to do its best to change the raw bit data of one data type to another.

"Coerce to type" is a much more intelligent conversion, which is what you need in this case.