n.-1 could be all faces, which is the current capability, but it would be great to define paths by the faces of the object hit as well as the simple fact of hitting that object.Īll that said, this is a great feature that really speeds up the subsequent path analysis and filtering as you don't have to lug GB of raytrace data around anymore. In addition, I would love to see path analysis extended to support n.f format filtering, where you don't just specify the object n that is hit but also the face of that object. It would be good to document the PAF file format.
WHAT IS A ZEMAX FILE SOFTWARE
Instead of exporting designs to restrictive file formats that remove vital information from the original file, the software creates shared files with complete design information. For users with existing ZRDs (which is all of them), there should be an option to save a PAF in the Path Analysis tool, so you can just load the ZRD you alreday have and generate a PAF.Ĥ. OpticsViewer software allows engineers to share, view, and validate native OpticStudio design files to ensure optical systems meet manufacturing requirements. For details on the SEQ2ZMX converter, see the text file SEQ2ZMX.TXT, also in the SEQ2ZMX directory. The SEQ2ZMX converter is located under the SEQ2ZMX directory off the main ZEMAX directory. I think it should load the PAF in preference to the ZRD, although clearly if there's no PAF then it should load the ZRDģ. Then, execute the SEQ2ZMX conversion utility to convert the file from SEQ to ZMX format. When you load the Path Analysis Tool after saving a PAF, but not generating a ZRD, you get: The docs should state where the PAF is stored. It really reduces the time of the workflow that generates ray paths in the system. It makes it much faster to generate the various paths, as a file of only a few kb gets generated, instead of some huge ZAR file.
0 kommentar(er)
