<Resending with attachment removed,  so the webinar is no longer this afternoon 
but is will be able to be viewed in the archive in a few days once it's 
uploaded.>

Just thought I'd mention that if NONMEM runs are initiated from a Phoenix 
session then the tables are automatically extracted from NONMEM runs and you 
can then post-process them in either Phoenix or tools of your choice including 
Xpose and PSN.  (importing NONMEM log files executed externally will also 
perform the same extracts).

There is a free webinar this afternoon that will demonstrate some of these 
Connect functions;  18 May: Time: 11AM New York (8AM San Francisco, 4PM London, 
5PM Paris
 https://pharsight.webex.com/pharsight/onstage/g.php?t=a&d=927440301  (if you 
can't make the time a recording and copy of the slides will be posted within a 
few days (e .g. 
http://www.pharsight.com/events/eventsonline_archive.php#replay_047 ) 

  With the release of Phoenix 6.2; with this release I think we've incorporated 
a lot of feedback from the previous releases in enhancing our interactions with 
 third-party applications including R, PSN, NONMEM etc. via Connect as well as 
our own analytical engines.  Local and remote grid runs are supported.

  For those of you attending PAGE, there is also a Phoenix Connect & NLME 
course prior to PAGE on the 6-7th June.  Full details can be found at ;  
http://www.pharsight.com/training/course_display_new.php?details_id=81 and you 
can sign up through this page.  A full Phoenix license will be provided for the 
course until the end of June.

   Please let Lindsay ([email protected]) or myself know if you have any 
questions, it would be great to meet you all for a few minutes during the 
meeting in Athens so please try to stop by our booth if you get the chance.

    Best regards,
                         Simon.
___________________________________
Senior Scientific Consultant
Pharsight- A Certara(tm) Company
31 March Phoenix 6.2, including the IVIVC toolkit is released, get tips and 
discuss Pharsight products with other users; 
www.pharsight.com/extranet<http://www.pharsight.com/extranet>
___________________________________
http://www.pharsight.com/training/training_upcoming.php
Population analysis with Phoenix v6.1 NLME : 6-7 Jun 2011, Athens, Greece 
(Before PAGE) Introduction to Phoenix v6.x: 12-14 September 2011 Amsterdam, NL.
IVIVC toolkit Phoenix v6.x: 14-15 September 2011 Amsterdam, NL.


-----Original Message-----
From: [email protected] [mailto:[email protected]] On 
Behalf Of AVG (Andreas Velsing Groth)
Sent: Tuesday, May 17, 2011 2:09 PM
To: 'Sebastien Bihorel'; nmusers
Subject: [NMusers] Table formatting in NONMEM7- can I skip the "Table No." 
header row?

Dear fellow Nmus,

Does anyone know whether I can make an output table with $TABLE skipping the 
"Table No. 1" row and going straight to the row with the actual column headers? 
The purpose is to ease import of the output table to other applications, 
particularly SAS.

I think that should be possible, but maybe some dirty tricks are required?

I consider this somewhat related to Sebastiens Q below.

_________________________________________________________________
NOTICE: The information contained in this electronic mail message is intended 
only for the personal and confidential use of the designated recipient(s) named 
above. This message may be an attorney-client communication, may be protected 
by the work product doctrine, and may be subject to a protective order. As 
such, this message is privileged and confidential. If the reader of this 
message is not the intended recipient or an agent responsible for delivering it 
to the intended recipient, you are hereby notified that you have received this 
message in error and that any review, dissemination, distribution, or copying 
of this message is strictly prohibited. If you have received this communication 
in error, please notify us immediately by telephone and e-mail and destroy any 
and all copies of this message in your possession (whether hard copies or 
electronically stored copies). Thank you.

Reply via email to