Error when reusing NCA model on new data set

I have made a workflow in which an input data set is reworked, and an NCA object is being executed. Then, the results is parsed to a table object where the relevant columns are summarized. I now wanted to reuse the process on a new data set; however, the NCA object keeps crashing ("unexpected error- don't save" etc.) and I cannot fit the slopes for each individual (if I try to click on individual profile start-end points, systems crashes).

If, instead, I copy the entire NCA object, reconnect input and output, that new object works fine and allows me, again, to go through each individual profile to select data points for use for the terminal half-life estimation, now on the new data set. This malfunction really takes out one of the advantages I had envisioned - reuse of a pre-defined process on a new data set. Any suggestion how to make this work without having to do this copy-and-paste of the NCA object? Thx Thomas

This sounds like it may be a bug. Please attach the project if possible, and we will investigate it. There may be a workaround if it is a bug. Did you apply data links and export the workflow as a template prior to reusing it with new data?

Attaching the project may be problematic. But - I did not save it as a template. I reused the old phx-file, then jimported a new data file, and connected that to the first input in the process....Would that corrupt the process?

How would I apply data link instead of the procedure describe?

Better yet, what I'd to do is to reuse the process on a new data set. How should I do that ,step-by-step? seems that I did something unquthorized here!

Thx Thomas

After you've completed a workflow that you'd like to reuse with new data, click on the workflow in the Object Browser to view the workflow diagram. Right-click in the blank workflow diagram and select "Connect External Sources to Data Links". A data link object will appear for every worksheet that you imported that was used in your workflow. Click on the data link in the object browser. If the new data doesn't have the same columns as the old data, remove the columns that aren't needed prior to exporting the workflow as a template using the "Remove" button. Re-execute the entire workflow by clicking on the workflow in the Object Browser and clicking the "Execute" button. Next, right-click on the workflow in the Object Browser and select "Export". Save the workflow as a .wnlt file. Next, make a new project and import the new data set(s). Import the template as you would import a data set. It appears as a nested workflow. Click on the data link in the object browser and drag your new data into the Main Mappings panel for the data link. Ensure that all orange columns have something mapped (e.g., Subj -> Subject, etc.). Then, execute the workflow in the new project.

Thomas - I know you are aware of the workaround but I thought I'd publish it here for everybody else; this is QC_PHX11067.

and was in the 6.2.1 release note as a "Known Issue". If an NCA model is re-mapped or an NCA template is re-used with a different source, the slopes may not display correctly and may generate an error. To workaround the issue, unmap and remap at least one sort key.

This is expected to be fixed in the 6.3 release (early 2012)

The issue was that some internal sheets retained info from the parent workflow used to create the template, by unmapping e.g. Subject and then re-mapping subject this forces a re build of the key IDs and clears the old data.

 Simon

We have had a couple of users report something similar to this on 8.1, if you encounter the same then this may be helpful.  Unexpected errors, are 'unknown unknowns' and that's why we give the warning message. If you do receive one of these it would be useful to send the logs, (find them under Help)

However these are notoriously difficult to track down and isolate and in my experience the vast majority do not cause further problems in the project upon re-execution, (For an extremely small minority the problems is almost always resolved by deleting the object (i.e. the Table) that is causing the issue and re-inserting).

SUPPORT-1506   an 'unexpected error' or similar is reported whilst trying to execute NCA, there is no obvious cause so re-executing is typically sucessful as a workaround.  if that doesn't work then you can;

1) save the project, (with a different name if you want )o you have the last 'good' copy still).

2) restart Phoenix

3) reopen your saved project.

4) re-execute, most likely it will work, if the error persists and no explanation is found in e.g. warnings or core output, then please raise a support case by emailing the project to support@certara.com, or if you do not want to share the project request a screen share to demonstrate the issue.

We wlll of course update you if we find a definitive solution, we have only had this reported in 8.1 so it might be fixed in a current release but until we understand the exact mechanism for 1504 in particular I don't want to recommend you upgrade.

To keep abreast of latest releases etc. i would suggest you follow key threads  e.g. https://support.cert...raining/?p=6287

Edited by Simon Davis, 06 October 2021 - 03:16 AM.