Pass the current iso name to Post Processor

Posted by: sylv7320

Pass the current iso name to Post Processor - 02/09/16 12:52 PM

I am trying to copy the Material / Sheet ID text file off after each iso run to use later to import data from each iso to a spool tracking database. I'd to somehow name each file copy with the iso name it is for.

Using a simple batch file to do the copy as a post processor is it possible to pass the name of the current iso being run as an argument?
Posted by: dgorsman

Re: Pass the current iso name to Post Processor - 02/09/16 01:08 PM

Should be possible, although not simple. The PISOGEN.INI file is passed as default to the pre- and post-processor routine. Both include the path to the ISOGEN.FLS file, which contains the various paths and naming conventions. You'd have to first parse out the FLS filename from the PISOGEN.INI contents, then parse out the material file from the FLS contents.

You might want to take a slightly different path, by cleaning out the output folder on each run. Then you can just reference a standardized file name.
Posted by: sylv7320

Re: Pass the current iso name to Post Processor - 02/09/16 01:31 PM

Thanks, I am realizing my plan won't work anyway if someone batches multiple isos at once. The output file will contain the spool data from all isos in the run. I think the file gets overwritten each time so I'll instead copy the MATLSHTID.txt file after each run to some other folder using a post processor batch file. There the new file could be named uniquely so as not to overwrite any others. Then I can import all files to a database to report the data.

I just need a way to weed out the previous data from isos being run more than once. Would the unique identifier tell me which iso data is the latest for a given iso if it shows up in more than one output file? I don't know what format it is in, can it be converted to something I can sort on? Example: F8EDC250-6039-482C-B0B4-41B1FDDBA00D.
Posted by: dgorsman

Re: Pass the current iso name to Post Processor - 02/09/16 03:31 PM

That's a GUID (globally unique ID), probably the UNIQUE-COMPONENT-IDENTIFIER component entry. Every component has one, and they are unique to that component for its lifetime e.g. open drawing, add component (GUID is assigned automatically), save and close drawing, re-open, value is still the same. Incidentally, when ISOGEN runs properly the GUID values should also be included as attributes in the iso drawing.