Dear all,
The Core Output in NCA behaves differently from previous versions.
If in a cross-over profiles were sorted by subject and treatment, whereas period and sequence mapped to sort, the order in the output was e.g.,
subject 1, treatment R, subject 1, treatment T, … subject n, treatment R, subject n, treatment T.
Given the time in the output, this was also the order of execution.
Perfect. For ages (since WNL 5.0) I use an R-script to shorten the output (deleting parameters I don’t need, some cosmetics, …) and could easily import it into my reports.
During validation of PHX 7.0 I saw a strange effect. Simple 3×3 cross-over dose proportionality study. The core output is a mess. I extracted the relevant lines (treatment/subject and time of execution).Tried to order by the execution time but I don’t see a pattern.
CoreTroubles.xls (33 KB)
Hi Helmut!
That’s really annoying finding 
I think this is a consequence of NCA running optimization
As you know now NCA in PHX 7.0 engine is taking different profiles not in turns but in parallel. It writes the out just as stdout I think..
Hmmm, I think PHX should sort the output data before putting in this file for the User’s convenience like in tabular format.
BR,
Mittyright
Hi Mittyright,
Yep. I’m not the only one scripting the core output. Of course, I could build nested lists in R and sort them – but currently PHX7.0 does not pass my validation. 
Your reasoning is clever.
Morning Helmut, Mitty,
This is noted as QC 16248
The profiles in the “Core Output” and “Warnings and Errors” text output can be in a different order after re-executing, i.e., they are put back together in the order they come back from different processors so this is random.
It should be fixed going forward, but I don’t have a time line for that currently.
Simon.
Please, is there something new with the NCA Core Output sorting problem?
Milan, as stated above - after investigation, it was found the issue lies in the code that builds the core output. In Phoenix 7.0 the parallelization caused this area of code to be refactored and hence the issue does not exist in Phoenix 1.4. There is no known workaround for this issue in Phoenix 7.
However this issue has been fixed in the next release; Phoenix 8.0 when addressing QC 16306 and 16248. ​
Simon.
Just so anyone following this thread is aware, this was confirmed in the Product Notification PHX-034 along with a few other issues that users should note. These can be found on the downloads page by expanding ‘Show details’.
Product Notification PHX-033 confirmed that Phoenix 7 was certified for Windows 10.
Simon.
Milan, apologies for the previous spam reply to your post but hopefully you saw this notificaion that the next release, Phoenix 8.0 will be launched in October.
https://support.certara.com/forums/topic/1100-phoenix-8-is-launching-on-october-3-2017/
Simon.
PS Also in the mean time for other users of Phoenix 7 please note there has also been another Product notification #35 released this month that I would recommend reading.
