Search the Community
Showing results for tags 'comparison'.
Found 3 results
-
Hello again! I have a simple IF condition here that fetches an attribute value from a geometry & prints a result according to the comparison but for some reason it's not behaving as expected. It's just 2 nodes & very simple yet as a non-programmer I'm scratching my head. If anyone can take a look & tell me what I did wrong I'd really appreciate it If_condition.hipnc
-
Hello, guys! I keep having an issue when I try to compare attributes from two distinct points. The VEX program tests if they are equal, like this: if(ptu == t_start) And although I see in the geometry spreadsheet that they are, the VEX code say they aren't. I thought It was a precision problem, so I rounded both values to a three float precision value //round t_start = rint(t_start * 1000)/1000; t_end = rint(t_end *1000)/1000; ptu = rint(ptu * 1000)/1000; This was the solution for some points and for others, the problem persisted. Some still have the same values in the spreadsheet and the VEX code interprets them as different values.- 2 replies
-
- 1
-
-
- float
- comparison
- (and 2 more)
-
Smoothing geometry on the GPU using OpenCL. In VEX it has to be done in 2 steps where the same thing can be achieved in OpenCL in one step using barriers [khronos.org]. For a 822K polygon model, it's over 500 times faster than VEX on GTX 970 for 1000 iterations, and over 600 times faster for 10K iterations. Timings are recorded separately as there seems to be some overhead when running them one after another. Special thanks to SESI.
