LabVIEW
NI Traffic Light CLD Soln vs mine
richjoh,
the point everyone else is trying to make, is that in a task that is fairly trivial, like the car wash example, it doesnt really count for much if you can solve the problem. What counts is the manner in which it is solved, i.e. how you would go about solving a much, much bigger project. If a person has sloppy code on a simple application then it is assumed that things would only go from bad to worse in a real project.
In four hours they cannot ask you to do anything really complicated so the give a simple-ish task and see you tackle that, and from that can infer your skill level. It is not a perfect system however.
The thing is, if you want to pass (and I have not even done CLAD so I shouldn't be commenting here) then you need to learn the rules to pass the exam (i.e. work the system). What I mean is, if you desire to achieve the end result of having a certification, you have to whatever is necessary to pass, regardless of your personal preferences. The irony is that working out what the rules are, and learning how to trick examiners into thinking you know exactly what is going on, actually ends up with you knowing what you should have known in the first place
my 5 pence
the point everyone else is trying to make, is that in a task that is fairly trivial, like the car wash example, it doesnt really count for much if you can solve the problem. What counts is the manner in which it is solved, i.e. how you would go about solving a much, much bigger project. If a person has sloppy code on a simple application then it is assumed that things would only go from bad to worse in a real project.
In four hours they cannot ask you to do anything really complicated so the give a simple-ish task and see you tackle that, and from that can infer your skill level. It is not a perfect system however.
The thing is, if you want to pass (and I have not even done CLAD so I shouldn't be commenting here) then you need to learn the rules to pass the exam (i.e. work the system). What I mean is, if you desire to achieve the end result of having a certification, you have to whatever is necessary to pass, regardless of your personal preferences. The irony is that working out what the rules are, and learning how to trick examiners into thinking you know exactly what is going on, actually ends up with you knowing what you should have known in the first place
my 5 pence
OK, now for an objective comparision here, lets compare my top level VI size to NI's top level VI... Take a look at the pic you will see my VI size is 3.65X smaller the NI VI... Hmmm, maybe if I added all that stuff there making up, uuuhmmm, I mean marking up it would be larger.. I guess 
One thing to mention:
The examples are probably saved with LabVIEW 7, thus the disc size is probably twice the size of an 8.x VI.
The scoring of the exam is written down:
Applications are graded on the following three criteria:
Passing grade is 75% or higher.
So if your documentatoin is bad (0 points) and your style is bad (0 points) you will fail.
I think your examples will pass, but I am not sure with how much.
If I tell more I would be violating my CLD agreement.
Ton
The examples are probably saved with LabVIEW 7, thus the disc size is probably twice the size of an 8.x VI.
The scoring of the exam is written down:
Applications are graded on the following three criteria:
- Functionality
- Programming style
- Documentation
Passing grade is 75% or higher.
So if your documentatoin is bad (0 points) and your style is bad (0 points) you will fail.
I think your examples will pass, but I am not sure with how much.
If I tell more I would be violating my CLD agreement.
Ton
LabVIEW user groep 
I think it's fairly obvious that this guy has made up his own mind, and no amount of discussion will sway him, regardless of the fact that it's coming from people with a combined amount of experience that must be in the centuries.
Oh well, I'm sure that he'll probably write up code that will happily keep someone else employed when they have to go and clean it up.
Oh well, I'm sure that he'll probably write up code that will happily keep someone else employed when they have to go and clean it up.
Please don't just show the file size, it is meaningless.
Show the itemized list from "VI properties...memory usage" before running (but after saving in the current version if upgrading or downgrading). A freshly up- or downconverted VI is often less efficient until saved again in the current version.
