Merging with Calypso pdf, Ghostscript

[[Ch...]]

I have a weird frustrating issue with GearPro, want to see if anyone else if seeing the same thing.  

For years I've stitched my GearPro reports to the end of my Calypso reports using PDF all (using GhostScript) save in Calypso.   Never had any issues with it.  

Recently, I've had a couple of programs that are failing to stitch together.  Its saving just the Calypso reports.  Even more frustrating, its not entirely repeatable.  It seems to happen more often on all tooth scans (reports are larger maybe causing issue?).  Also, if I restart Calypso and GearPro it will almost always correctly stitch the first one just find, but subsequent runs may not stitch. 

 

I know this isn't necessarily a GearPro issue, but has anyone seen this before? 

[[DW...]]

Please sign in to view this username.

 I have absolutely no experience with Ghostscript, GearPro, or even gears. I did a quick a quick search on here about how people are using Ghostscipt, and it seems some people are using it with PCM. This part stood out to me - 

Please sign in to view this quote.

In most scripts (the good ones at least), there is error handling to include timeout logic for a function, and if the function cannot be completed within a certain amount of time, it will silently fail and continue processing the script. This prevents a script from hanging. Perhaps there is a timeout setting being tripped where GearPro PDF is not fully written before stitching starts? Perhaps adding a delay in the script or with PCM will fix the timing issue. 

 

Please sign in to view this quote.

This is interesting, and may point to temp files not being cleaned up correctly (or maybe Ghostscript runs out of memory or hits temp file limits?)

When the stitching fails, is the GearPro PDF already generated? Or does it generate seconds AFTER Ghostscript completes the stitching?

[[Ch...]]

Please sign in to view this username.

Please sign in to view this quote.

This is what I'm leaning towards.  Especially since it seems to happen on all teeth scans, which are by definition, larger than the 4 tooth scans.  

 

Please sign in to view this quote.

My next step is to carefully track exactly when GearPro finishes generating the report, haven't had time to test it today.  I should be able to check the report status window to narrow down exactly where Calypso is in the report phase.

 

I'm using the function below in Calypso:

I've looked thru the GhostScript documentation, but without knowing exactly how Zeiss implements it I can't see exactly what the triggers are or when it times out.  

 

 

I was hoping for an easy button where someone else had seen the exact same thing.  

 

 

[[Ri...]]

Any reason you don't use the PiWeb Report where GearPro pushes the data to Calypso - including the PDF images which are then embedded into the report?

[[Ch...]]

Please sign in to view this quote.

There's a bit of grandma's ham fallacy here.  Its just the way we've always done it.  

In fact, I do push the GearPro results to PiWeb and embed them in the reports.  But the gear reports display very small in the PiWeb template I use.  But I also use ghostscript to stitch the full size reports to the end of the PiWeb pdf.  

Now, i will have to edit my PiWeb template to display the reports bigger.  And I'll probably want to save it as its own template, that way I don't get any unintended issues on other programs that use that PiWeb template.  Then I'll have to troubleshoot any formatting issues that invariably pop up with PiWeb.  

I love PiWeb and I hate PiWeb.  I love all the options and my custom reports for some parts looks really amazing; but too often it goes against my Occam's Razor approach.  Why would I spend all day editing/testing a template when I could accomplish the same thing by just clicking a checkbox.