Skip to main content
Solved

How to stop NSTR from resetting number of cores?

  • July 20, 2023
  • 1 reply
  • 112 views

William Oak
Forum|alt.badge.img

Hello,

So I’ve been trying to alter the number of cores through a macro by using “SYSP 901, []”. However, each time I run the ray trace (NSTR 1, 0, 0, 0, 0, 0, 0), the number of cores resets to its maximum value.

To attempt to identify why, I re-used the code proposed HERE, adding a “print SYPR(901)”, and I get the following.

The elapsed time varies somewhat, but stays close enough to one another to conclude that the NSTR is somehow resetting the # of core before running the ray trace.

-The duration is coherent with 20 cores (~7.8s) if I run it using the Ray Trace Control window; the time at 1 core is ~40s, 16 cores 7.4 s

-I’ve tried using the advanced options in the system explorer to Turn Off Threading, without it having any apparent effect.

-Apparently NSTR does an update to everything before running, but I’ve not been able to reproduce the bug with “UPDATE” so I don't think that's the cause.

-I’ve tried other files and seen the same issue (namely Projector Modeled Using an IES Data File.ZDA from the samples).

Any ideas as to the cause? I might have missed something in the help, as the related terms (Threads, Core and CPU) are used almost interchangeably and there might be a term I’ve not seen.

 

 

Best answer by William Oak

As a follow-up to close this, there was a bug in the zemax version I used, solved in R2.0.

View original
Did this topic help you find an answer to your question?

1 reply

William Oak
Forum|alt.badge.img
  • Author
  • Infrared
  • 10 replies
  • Answer
  • July 25, 2023

As a follow-up to close this, there was a bug in the zemax version I used, solved in R2.0.


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings