[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Returned mail: warning: cannot send message for 4 hours





This is a MIME-encapsulated message

--IAA01931.795704595/gsusgi1.Gsu.EDU

    **********************************************
    **      THIS IS A WARNING MESSAGE ONLY      **
    **  YOU DO NOT NEED TO RESEND YOUR MESSAGE  **
    **********************************************

The original message was received at Mon, 20 Mar 1995 03:51:43 -0500
from bnl.gov [130.199.128.163]

   ----- The following addresses had delivery problems -----
phygap@petitt.phy-astr.gsu.edu  (transient failure)
    (expanded from: <phygap@gsusgi1.gsu.edu>)

   ----- Transcript of session follows -----
phygap@petitt.phy-astr.gsu.edu... Deferred: Connection timed out with petitt.phy-astr.gsu.edu.
Warning: message still undelivered after 4 hours
Will keep trying until message is 5 days old

   ----- Original message follows -----

--IAA01931.795704595/gsusgi1.Gsu.EDU
Content-Type: message/rfc822

Return-Path: phenix-comp-l@bnl.gov
Received: from bnl.gov (bnl.gov [130.199.128.163]) by gsusgi1.Gsu.EDU (8.6.10/8.6.10) with SMTP id DAA01258 for <phygap@gsusgi1.gsu.edu>; Mon, 20 Mar 1995 03:51:43 -0500
Received: by bnl.gov (5.57/Ultrix3.0-C)
	id AA06920; Mon, 20 Mar 95 04:05:23 -0500
Date: Mon, 20 Mar 95 04:05:23 -0500
Message-Id: <199503200849.DAA01203@gsusgi1.Gsu.EDU>
Comment: PHENIX Computing
Originator: phenix-comp-l@bnl.gov
Errors-To: tcarey@p2tacs.lanl.gov
Reply-To: <phenix-comp-l@bnl.gov>
Sender: phenix-comp-l@bnl.gov
Version: 5.5 -- Copyright (c) 1991/92, Anastasios Kotsikonas
From: Mail Delivery Subsystem <MAILER-DAEMON@gsusgi1.gsu.edu>
To: Multiple recipients of list <phenix-comp-l@bnl.gov>
Subject: Returned mail: warning: cannot send message for 4 hours

This is a MIME-encapsulated message

--DAA01203.795689379/gsusgi1.Gsu.EDU

    **********************************************
    **      THIS IS A WARNING MESSAGE ONLY      **
    **  YOU DO NOT NEED TO RESEND YOUR MESSAGE  **
    **********************************************

The original message was received at Sun, 19 Mar 1995 23:43:54 -0500
from bnl.gov [130.199.128.163]

   ----- The following addresses had delivery problems -----
phygap@petitt.phy-astr.gsu.edu  (transient failure)
    (expanded from: <phygap@gsusgi1.gsu.edu>)

   ----- Transcript of session follows -----
phygap@petitt.phy-astr.gsu.edu... Deferred: Connection timed out with petitt.phy-astr.gsu.edu.
Warning: message still undelivered after 4 hours
Will keep trying until message is 5 days old

   ----- Original message follows -----

--DAA01203.795689379/gsusgi1.Gsu.EDU
Content-Type: message/rfc822

Return-Path: phenix-comp-l@bnl.gov
Received: from bnl.gov (bnl.gov [130.199.128.163]) by gsusgi1.Gsu.EDU (8.6.10/8.6.10) with SMTP id XAA26205 for <phygap@gsusgi1.gsu.edu>; Sun, 19 Mar 1995 23:43:54 -0500
Received: by bnl.gov (5.57/Ultrix3.0-C)
	id AA06293; Sun, 19 Mar 95 23:57:08 -0500
Date: Sun, 19 Mar 95 23:57:08 -0500
Message-Id: <01HOC59EYVAQ8X5QG2@ctrvax.Vanderbilt.Edu>
Comment: PHENIX Computing
Originator: phenix-comp-l@bnl.gov
Errors-To: tcarey@p2tacs.lanl.gov
Reply-To: <phenix-comp-l@bnl.gov>
Sender: phenix-comp-l@bnl.gov
Version: 5.5 -- Copyright (c) 1991/92, Anastasios Kotsikonas
From: MAGUIRC@ctrvax.vanderbilt.edu
To: Multiple recipients of list <phenix-comp-l@bnl.gov>
Subject: Event reconstruction CPU execution times for PHENIX central arms

							March 19, 1995

Dear PHENIX software colleagues,

	Below an updated table of current CPU execution times for single HIJET
density event reconstruction in the central PHENIX arms.  The table now
includes my RS6000 340D and Soren Sorensen's SGI 4400SC at ORNL.  A CPU timer
was put inside of PISORP for more accurate times, and no NTUPLE store options
were invoked.  The times below are based on 10 events and include pole tip
background flux. 

 		Event Reconstruction CPU Times/Event (Seconds in PISORP)

        PISORP			Platform
    Data Structures	RS6000		SGI 4400SC      (DC/PC tracking mode)

	DC/PC1             7.6              3.6         ("known track mode")
	DC/PC1            33.6             12.3         ("unknown track mode")

      DC/PC1/RICH          8.1              4.7         ("known track mode")

    DC/PC1/RICH/PC2/PC3   12.1              6.3           ""     ""   ""

 DC/PC1/RICH/PC2/TEC/PC3 169.7             49.7           ""     ""   ""

	A triplet of comments:

	1) The SGI 4400SC has a dual cache system, and this apparently works
           to its advantage in the TEC reconstruction compared to the simple
           single cache IBM system;

	2) The pattern recognition here is based on a DC1/DC2 8 stereo wire
           implementation leading to what has been called the "stepping-stone"
           approach to the full track reconstruction.  This method will not
           work with a DC2 only stereo system, so the above times are not
           guaranteed in that case;

	3) There may be as much as a factor of two fat in the DC/PC1 CPU times
           for the "unknown" track mode, but that is not worth pursuing at the
           moment.

	Note that the EMCal is not yet in this event reconstruction, but Gabor
David has done an extensive set of in-PISA cluster reconstructions.  So we
should already have a good handle on this last major time component of the
central arm event reconstruction. 

Best regards,
Charlie Maguire

PS to Nikolai:  Could you forward to me the event reconstruction times in
single HIJET density from your stand-alone program, broken out in the same
detail as the table above and specifying the platform?  Thanks. 


--DAA01203.795689379/gsusgi1.Gsu.EDU--



--IAA01931.795704595/gsusgi1.Gsu.EDU--