detailRoute vs trialRoute

Thanks for the feedback on the reasons why trialRoute vs. detaiRoute comparison would be useful.  I will pass this along to our developers.  In parallel with that, I'd encourage you to file an enhancement request with the Cadence support folks you work directly with on an ongoing basis, or on http://support.cadence.com

You're right that the trialRoute lengths with the script example I shared would need to be stored (via a hash table or a side file) in order to use it to compare to detailRoute.

Half-perimeter net lengths are (I believe) what are stored in dbNetLenX/dbNetLenY so I don't think it needs to be recalculated on the fly.  I could be wrong on that though.

I can see there being complexity in implementing what you're requesting from our developer's perspective.  Say for example, someone runs trialRoute and then edits the routes manually.  Then they save the design and exit the tool.  Then they restore the design.  Then later, at some point, they call reportRoute and want it to compare trialRoute to detailRoute.  I can see it being non-trivia for the trialRouted lengths to be accurate and persistent in this scenario.

I hope this helps understand why this isn't straightforward.  Thanks for raising this issue- even if we don't have this capability straight away, I think it's useful to understand the subject a little better and know what options are/aren't available if you or other users are working in this space.

Thanks for the feedback on the reasons why trialRoute vs. detaiRoute comparison would be useful.  I will pass this along to our developers.  In parallel with that, I'd encourage you to file an enhancement request with the Cadence support folks you work directly with on an ongoing basis, or on http://support.cadence.com

You're right that the trialRoute lengths with the script example I shared would need to be stored (via a hash table or a side file) in order to use it to compare to detailRoute.

Half-perimeter net lengths are (I believe) what are stored in dbNetLenX/dbNetLenY so I don't think it needs to be recalculated on the fly.  I could be wrong on that though.

I can see there being complexity in implementing what you're requesting from our developer's perspective.  Say for example, someone runs trialRoute and then edits the routes manually.  Then they save the design and exit the tool.  Then they restore the design.  Then later, at some point, they call reportRoute and want it to compare trialRoute to detailRoute.  I can see it being non-trivia for the trialRouted lengths to be accurate and persistent in this scenario.

I hope this helps understand why this isn't straightforward.  Thanks for raising this issue- even if we don't have this capability straight away, I think it's useful to understand the subject a little better and know what options are/aren't available if you or other users are working in this space.