November 2001 Email Thread
**************************************************************************
**************************************************************************
X-Authentication-Warning: apollo.gat.com: majordom set sender to
owner-nfc-sc01@fusion.gat.com using -f
Date: Fri, 02 Nov 2001 20:55:13 -0500
From: "Thomas W. Fredian"
X-Accept-Language: en
To: Kate Keahey
CC: nfc-sc01@fusion.gat.com
Subject: Re: summary of telecon today
Sender: owner-nfc-sc01@fusion.gat.com
Status:
Hard to tell not knowing what's causing the bug! We'll just have to wait and see :-)
-tom
Kate Keahey wrote:
> Tom,
>
> Many thanks! What changes will need to be made to the demo after you fix
> the bug? I asked Charles to set up the credentials and the gridmapfile.
>
> At 08:39 PM 11/2/2001 -0500, Thomas W. Fredian wrote:
> >Here is the current status of the work.
> >
> >1) The IDL visualization problem with the data being written by efit is a very
> >obscure bug. It appears that some of the data is getting corrupted somehow
> >which is causing some of the computations done in the IDL animation code
> >to get into an infinite compute loop. I believe I will be able to work on this
> >without
> >the sc computers next week. In the mean time we do have a working demo which
> >is reading from the datafiles that don't have this problem.
> >
> >2) I've added the checking for the status in the netlogger calls and
> >re-establish
> >the connection to the NetLogger if the writes fail and re-attempt the writes.
> >
> >3) Qian has installed the efit program on the sc cluster and it works fine!
> >I've set it up to run from my account for the demo. IMPORTANT>> Apparently,
> >the sc cluster is not recognizing the scdemo credentials. There is no map
> >for the
> >scdemo credential to my account in the gridmap file. < >
> >Mary,
> >
> > I've put an scemo-idl.tgz in diesel.lbl.gov:~twf which has the NetLogger
> >instrumented controller. On natasha you will need to:
> ># cd /usr/local/fusionDemo/idl
> ># tar zxf scdemo-id.tgz
> >
> >If you want to run the controller with the NetLogger you'll need to add a
> >line to
> ># echo 'netlogger_server terra.mcs.anl.gov:14835' >>
> >/usr/local/fusionDemo/config/envsyms
> >
> >-tom
> >
> >Kate Keahey wrote:
> >
> > > All,
> > >
> > > we had the last telecon related to the sc demo today, so I am posting a
> > > summary of issues since they will have to be resolved on this list now.
> > > Please let me know if I forgot about something (practically a given ;-) or
> > > correct me if I misrepresented something.
> > >
> > > Fist some loose ends pertaining to the demo:
> > >
> > > 1) Qian and Tom are trying to make the IDL visualization work with data
> > > that is actually produced by efit (as opposed to the slightly "fake"
> > > approach we are using now). Qian will get an account on the Argonne sc
> > > machines, and will try to resolve it. If necessary she can also reproduce
> > > the problem on Tom's workstation so this can be worked on even after the sc
> > > machines are shipped if necessary.
> > >
> > > 2) Tom will add a check for write status to the netlogger writes
> > >
> > > 3) Qian will install efit on the Argonne sc cluster so we have a backup if
> > > the network goes down.
> > >
> > > 4) Chris will make some animations of the visualization of the data
> > > produced by efit and they will be accessible via a webpage. They require no
> > > special hardware or software beyond what comes with Windows to run. Chris
> > > will also send some explanations and images to David to produce a handout
> > > for the visualization part. Kate and Mary will meet with David on Sunday
> > > and get updated on what Fusion scientists want from visualization, and the
> > > ground breaking achievements this collaboratory will produce so they can
> > > later convincingly pretend to know something about it.
> > >
> > > The place to change default settings for the netlogger, database and efit
> > > is /home/twf/fusion/fusionDemo/config/envsyms (Tom, if I ever ask you
> > > again, which no doubt will happen, feel free to bounce this email to me
> > > ;-). Or they can be changed at command line.
> > >
> > > We also discussed some things that we see as accomplishments/interesting
> > > things about this demo. Here is a summary. Feel free to
> > add/delete/disagree.
> > >
> > > 1. development
> > > - development comprised globus extensions to MDSplus and a couple of 10
> > > line shell scripts
> > > - took ~ 2 weeks
> > > - by application scientists
> > > - expert in application-specific software but with no previous exposure to
> > > globus
> > >
> > > 2. what this software represents
> > > - a real first step towards creating a fusion grid; the software will no
> > > doubt evolve, but on the existing base (as opposed to being replaced)
> > > - the components developed to gridify efit will be reused to gridify other
> > > Fusion applications, efit was a proof of concept
> > > - this is not a throwaway prototype
> > >
> > > 3. value added
> > > - the most important thing added over what MDSplus already had was secure
> > > environment
> > >
> > > 4. what made all this possible
> > > - the Fusion community was ready for grids (had the foresight, approach,
> > > software, expertise, need...) so that the port to grids was an extension of
> > > an existing approach rather than a revolution
> > > - we have the right grid abstractions to do this kind of thing (
> > > non-invasive, but right amount of functionality)
> > >
> > > 5. technical aspects
> > > - port to Globus 2.0 was relatively easy
> > >
> > > Did I omit anything?
> > >
> > > __________________________
> > > Dr. Kate Keahey
> > > Math & Computer Science Div.
> > > Argonne National Laboratory
> > > Argonne, IL 60439, USA
> > > (630) 252-1673
> > >
> > >
> > ===============================================================================
> > >
> > > This message was sent to the SciDAC National Fusion Collaboratory (NFC)
> > > workers list nfc-sc01. Visit the Collaboratory at
> > > .
> > >
> > > To unsubscribe from this list, please send a message to
> > > majordomo@fusion.gat.com with the following text in the *body* of the
> > > message: unsubscribe nfc-sc01
> > >
> > > David P. Schissel:
> >
>
> __________________________
> Dr. Kate Keahey
> Math & Computer Science Div.
> Argonne National Laboratory
> Argonne, IL 60439, USA
> (630) 252-1673
===============================================================================
This message was sent to the SciDAC National Fusion Collaboratory (NFC)
workers list nfc-sc01. Visit the Collaboratory at
.
To unsubscribe from this list, please send a message to
majordomo@fusion.gat.com with the following text in the *body* of the
message: unsubscribe nfc-sc01
David P. Schissel:
**************************************************************************
**************************************************************************
X-Authentication-Warning: apollo.gat.com: majordom set sender to
owner-nfc-sc01@fusion.gat.com using -f
X-Sender: keahey@localhost
Date: Fri, 02 Nov 2001 19:52:26 -0600
To: "Thomas W. Fredian"
From: Kate Keahey
Subject: Re: summary of telecon today
Cc: nfc-sc01@fusion.gat.com
Sender: owner-nfc-sc01@fusion.gat.com
Status:
Tom,
Many thanks! What changes will need to be made to the demo after you fix
the bug? I asked Charles to set up the credentials and the gridmapfile.
__________________________
Dr. Kate Keahey
Math & Computer Science Div.
Argonne National Laboratory
Argonne, IL 60439, USA
(630) 252-1673
===============================================================================
This message was sent to the SciDAC National Fusion Collaboratory (NFC)
workers list nfc-sc01. Visit the Collaboratory at
.
To unsubscribe from this list, please send a message to
majordomo@fusion.gat.com with the following text in the *body* of the
message: unsubscribe nfc-sc01
David P. Schissel:
**************************************************************************
**************************************************************************
X-Authentication-Warning: apollo.gat.com: majordom set sender to
owner-nfc-sc01@fusion.gat.com using -f
Date: Fri, 02 Nov 2001 20:39:40 -0500
From: "Thomas W. Fredian"
X-Accept-Language: en
To: Kate Keahey
CC: nfc-sc01@fusion.gat.com
Subject: Re: summary of telecon today
Sender: owner-nfc-sc01@fusion.gat.com
Status:
Here is the current status of the work.
1) The IDL visualization problem with the data being written by efit is a very
obscure bug. It appears that some of the data is getting corrupted somehow
which is causing some of the computations done in the IDL animation code
to get into an infinite compute loop. I believe I will be able to work on this
without
the sc computers next week. In the mean time we do have a working demo which
is reading from the datafiles that don't have this problem.
2) I've added the checking for the status in the netlogger calls and re-establish
the connection to the NetLogger if the writes fail and re-attempt the writes.
3) Qian has installed the efit program on the sc cluster and it works fine!
I've set it up to run from my account for the demo. IMPORTANT>> Apparently,
the sc cluster is not recognizing the scdemo credentials. There is no map for the
scdemo credential to my account in the gridmap file. <>
/usr/local/fusionDemo/config/envsyms
-tom
Kate Keahey wrote:
> All,
>
> we had the last telecon related to the sc demo today, so I am posting a
> summary of issues since they will have to be resolved on this list now.
> Please let me know if I forgot about something (practically a given ;-) or
> correct me if I misrepresented something.
>
> Fist some loose ends pertaining to the demo:
>
> 1) Qian and Tom are trying to make the IDL visualization work with data
> that is actually produced by efit (as opposed to the slightly "fake"
> approach we are using now). Qian will get an account on the Argonne sc
> machines, and will try to resolve it. If necessary she can also reproduce
> the problem on Tom's workstation so this can be worked on even after the sc
> machines are shipped if necessary.
>
> 2) Tom will add a check for write status to the netlogger writes
>
> 3) Qian will install efit on the Argonne sc cluster so we have a backup if
> the network goes down.
>
> 4) Chris will make some animations of the visualization of the data
> produced by efit and they will be accessible via a webpage. They require no
> special hardware or software beyond what comes with Windows to run. Chris
> will also send some explanations and images to David to produce a handout
> for the visualization part. Kate and Mary will meet with David on Sunday
> and get updated on what Fusion scientists want from visualization, and the
> ground breaking achievements this collaboratory will produce so they can
> later convincingly pretend to know something about it.
>
> The place to change default settings for the netlogger, database and efit
> is /home/twf/fusion/fusionDemo/config/envsyms (Tom, if I ever ask you
> again, which no doubt will happen, feel free to bounce this email to me
> ;-). Or they can be changed at command line.
>
> We also discussed some things that we see as accomplishments/interesting
> things about this demo. Here is a summary. Feel free to add/delete/disagree.
>
> 1. development
> - development comprised globus extensions to MDSplus and a couple of 10
> line shell scripts
> - took ~ 2 weeks
> - by application scientists
> - expert in application-specific software but with no previous exposure to
> globus
>
> 2. what this software represents
> - a real first step towards creating a fusion grid; the software will no
> doubt evolve, but on the existing base (as opposed to being replaced)
> - the components developed to gridify efit will be reused to gridify other
> Fusion applications, efit was a proof of concept
> - this is not a throwaway prototype
>
> 3. value added
> - the most important thing added over what MDSplus already had was secure
> environment
>
> 4. what made all this possible
> - the Fusion community was ready for grids (had the foresight, approach,
> software, expertise, need...) so that the port to grids was an extension of
> an existing approach rather than a revolution
> - we have the right grid abstractions to do this kind of thing (
> non-invasive, but right amount of functionality)
>
> 5. technical aspects
> - port to Globus 2.0 was relatively easy
>
> Did I omit anything?
>
> __________________________
> Dr. Kate Keahey
> Math & Computer Science Div.
> Argonne National Laboratory
> Argonne, IL 60439, USA
> (630) 252-1673
>
> ===============================================================================
>
> This message was sent to the SciDAC National Fusion Collaboratory (NFC)
> workers list nfc-sc01. Visit the Collaboratory at
> .
>
> To unsubscribe from this list, please send a message to
> majordomo@fusion.gat.com with the following text in the *body* of the
> message: unsubscribe nfc-sc01
>
> David P. Schissel:
===============================================================================
This message was sent to the SciDAC National Fusion Collaboratory (NFC)
workers list nfc-sc01. Visit the Collaboratory at
.
To unsubscribe from this list, please send a message to
majordomo@fusion.gat.com with the following text in the *body* of the
message: unsubscribe nfc-sc01
David P. Schissel:
**************************************************************************
**************************************************************************
X-Authentication-Warning: apollo.gat.com: majordom set sender to
owner-nfc-sc01@fusion.gat.com using -f
X-Sender: keahey@localhost
Date: Fri, 02 Nov 2001 15:08:45 -0600
To: nfc-sc01@fusion.gat.com
From: Kate Keahey
Subject: summary of telecon today
Sender: owner-nfc-sc01@fusion.gat.com
Status:
All,
we had the last telecon related to the sc demo today, so I am posting a
summary of issues since they will have to be resolved on this list now.
Please let me know if I forgot about something (practically a given ;-)
or correct me if I misrepresented something.
Fist some loose ends pertaining to the demo:
1) Qian and Tom are trying to make the IDL visualization work with data
that is actually produced by efit (as opposed to the slightly "fake"
approach we are using now). Qian will get an account on the Argonne sc
machines, and will try to resolve it. If necessary she can also
reproduce the problem on Tom's workstation so this can be worked on even
after the sc machines are shipped if necessary.
2) Tom will add a check for write status to the netlogger writes
3) Qian will install efit on the Argonne sc cluster so we have a backup
if the network goes down.
4) Chris will make some animations of the visualization of the data
produced by efit and they will be accessible via a webpage. They require
no special hardware or software beyond what comes with Windows to run.
Chris will also send some explanations and images to David to produce a
handout for the visualization part. Kate and Mary will meet with David
on Sunday and get updated on what Fusion scientists want from
visualization, and the ground breaking achievements this collaboratory
will produce so they can later convincingly pretend to know something
about it.
The place to change default settings for the netlogger, database and
efit is /home/twf/fusion/fusionDemo/config/envsyms (Tom, if I ever ask
you again, which no doubt will happen, feel free to bounce this email to
me ;-). Or they can be changed at command line.
We also discussed some things that we see as accomplishments/interesting
things about this demo. Here is a summary. Feel free to
add/delete/disagree.
1. development
- development comprised globus extensions to MDSplus and a couple of 10 line shell scripts
- took ~ 2 weeks
- by application scientists
- expert in application-specific software but with no previous exposure to globus
2. what this software represents
- a real first step towards creating a fusion grid; the software will no
doubt evolve, but on the existing base (as opposed to being replaced)
- the components developed to gridify efit will be reused to gridify
other Fusion applications, efit was a proof of concept
- this is not a throwaway prototype
3. value added
- the most important thing added over what MDSplus already had was secure environment
4. what made all this possible
- the Fusion community was ready for grids (had the foresight, approach,
software, expertise, need...) so that the port to grids was an extension
of an existing approach rather than a revolution
- we have the right grid abstractions to do this kind of thing (non-invasive,
but right amount of functionality)
5. technical aspects
- port to Globus 2.0 was relatively easy
Did I omit anything?
__________________________
Dr. Kate Keahey
Math & Computer Science Div.
Argonne National Laboratory
Argonne, IL 60439, USA
(630) 252-1673
===============================================================================
This message was sent to the SciDAC National Fusion Collaboratory (NFC)
workers list nfc-sc01. Visit the Collaboratory at
.
To unsubscribe from this list, please send a message to
majordomo@fusion.gat.com with the following text in the *body* of the
message: unsubscribe nfc-sc01
David P. Schissel:
**************************************************************************
**************************************************************************
X-Authentication-Warning: apollo.gat.com: majordom set sender to
owner-nfc-sc01@fusion.gat.com using -f
Date: Thu, 1 Nov 2001 22:38:55 -0800
To: nfc-sc01@fusion.gat.com
From: "David P. Schissel"
Subject: Visualization for SC01
Sender: owner-nfc-sc01@fusion.gat.com
Status:
All,
Kate's telecon message reminds me that Chris informed me last
week at IEEE Vis of new images for our SC01 visualization.
If I understand correctly, the latest have been placed at
http://www.sci.utah.edu/sci_images/images13.html
The images tokamak20-23 are a good representation.
I suggest that we have our visualization discussion
tomorrow centered around these images.
- david
===============================================================================
This message was sent to the SciDAC National Fusion Collaboratory (NFC)
workers list nfc-sc01. Visit the Collaboratory at
.
To unsubscribe from this list, please send a message to
majordomo@fusion.gat.com with the following text in the *body* of the
message: unsubscribe nfc-sc01
David P. Schissel:
**************************************************************************
**************************************************************************
X-Authentication-Warning: apollo.gat.com: majordom set sender to
owner-nfc-sc01@fusion.gat.com using -f
X-Sender: keahey@localhost
Date: Thu, 01 Nov 2001 17:36:23 -0600
To: nfc-sc01@fusion.gat.com
From: Kate Keahey
Subject: telecon tomorrow
Sender: owner-nfc-sc01@fusion.gat.com
Status:
This is a remainder for a telecon for tomorrow, Friday, November 2nd at
11am CST for the duration of one hour.
8 domestic lines can call into 1-888-790-1415
Pass code:75284
Since the machines are shipping today/tomorrow this will be the last sc telecon I think.
Send me agenda items, so far I have:
1) netviz status: what works, what doesn't, what still needs to be done,
installation issues in lbl booth, etc.
2) general demo status: things that can change, demo configurations, troubleshooting experiences
3) status of scientific visualization?
Kate
===============================================================================
This message was sent to the SciDAC National Fusion Collaboratory (NFC)
workers list nfc-sc01. Visit the Collaboratory at
.
To unsubscribe from this list, please send a message to
majordomo@fusion.gat.com with the following text in the *body* of the
message: unsubscribe nfc-sc01
David P. Schissel:
**************************************************************************
**************************************************************************
X-Authentication-Warning: apollo.gat.com: majordom set sender to
owner-nfc-sc01@fusion.gat.com using -f
Date: Thu, 01 Nov 2001 12:19:21 -0500
From: "Thomas W. Fredian"
X-Accept-Language: en
To: Kate Keahey
CC: nfc-sc01@fusion.gat.com
Subject: Re: vizapp
Sender: owner-nfc-sc01@fusion.gat.com
Status:
I have NetLogger connections working on a03n, dg0n7 and natasha so far. I've made
MDSplus functions: NetLoggerOpen(), NetLoggerJobStatus(), NetLoggerTransfer() and
NetLoggerClose(), for operating the vizapp. Can you make some suggestions on how to
instrument the demo? Who should be sending the JOB STATUS messages? The controller,
the efit script and/or the MDSplus servers? Likewise on the TransferPerfTotal
messages? What should I put for BW.CURRENT and BW.AVG???? I don't have any good way
to compute these. What are the units of these anyway?
-tom
Kate Keahey wrote:
> Hi,
>
> I need help instrumenting the demo with calls to viz app, please read.
>
> We are making progress with the application visualizing interactions during
> the demo to the point where I think it makes sense to instrument the demo.
> Right now what we mainly see are little red circles appearing in
> appropriate parts of the country when computation is started, so nothing
> exciting but it looks like we'll get there. The demo can be instrumented by
> putting calls reporting on events in the body of demo components when those
> events happen (so for example when efit writes out data, we report on this
> event and it will be visualized). There is one problems with instrumenting
> the demo: unfortunately the Netlogger (which has to be used in order for
> things to work with this application) does not have a C shell API. I could
> either write a little program callable from Tom's script or we could push
> the calls into components for which we do have API. Let me know which you
> would prefer. I wrote a little program generating events for our demo with
> lots of comments on how the demo needs to be instrumented (this is the one
> we use for debugging the app); it is accessible at ~keahey/publish on
> either the datagrid cluster or sc desksides.
>
> Here is how this app works. The interactions are based on a piece of
> software called Netlogger (see http://www-didc.lbl.gov/NetLogger/). It
> implements a database where we can post events. Then the vizapp gets the
> events from there and visualizes them. We need to worry about the first
> part of the interaction only. Right now and for the next few days the
> database will be running on terra.mcs.anl.gov reading from port 14835 (see
> example). At SC it will move to the floor, so it should be configurable.
>
> In order to instrument a program, insert calls opening and closing
> connection to the netlogger at the beginning and end of the program (see
> example for C API to do this, I will be happy to provide examples in other
> languages or you can go to the url below). Then insert calls writing events
> pretty much as they are in the example in the appropriate places (it should
> be pretty much cut and paste from the example). Compile with netlogger
> header file and library; on the datagrid cluster and sc desksides the
> Netlogger installation is in ~keahey/NetLogger-1.6/linux.bin. Mary, I am
> not sure if you have it on diesel or natasha, installation is essentially
> just a matter of unpacking. Or I could do it for you if you tell me where.
>
> Further info: we are publishing two kinds of events (I took some shortcuts
> to make things easy so for example bandwidth info is "made up"):
>
> 1) JOB_STATUS, format: "ID=%s FRIENDLY.NAME=%s identifier> JOB.HOST=%s JOBS.SUBMITTED=%d
> JOBS.COMPLETE=%d JOBS.FAILED=%d BYTES.PRODUCED=%d"
>
> 2) "TransferPerfTotal", format: "ID=%s FRIENDLY.NAME=%s identifier> URL.SOURCE=%s URL.DEST=%s BYTES=%d BW.CURRENT=%f BW.AVG=%f"
>
> Here is the help I need:
>
> 1) Tom and Qian, since you know best where the event generating things
> happen in your programs, could you inert the appropriate calls from the
> example?
> 2) Mary, could you handle the installation on diesel and natasha?
>
> Kate
>
> ===============================================================================
>
> This message was sent to the SciDAC National Fusion Collaboratory (NFC)
> workers list nfc-sc01. Visit the Collaboratory at
> .
>
> To unsubscribe from this list, please send a message to
> majordomo@fusion.gat.com with the following text in the *body* of the
> message: unsubscribe nfc-sc01
>
> David P. Schissel:
===============================================================================
This message was sent to the SciDAC National Fusion Collaboratory (NFC)
workers list nfc-sc01. Visit the Collaboratory at
.
To unsubscribe from this list, please send a message to
majordomo@fusion.gat.com with the following text in the *body* of the
message: unsubscribe nfc-sc01
David P. Schissel:
**************************************************************************
**************************************************************************
X-Authentication-Warning: apollo.gat.com: majordom set sender to
owner-nfc-sc01@fusion.gat.com using -f
X-Sender: keahey@localhost
Date: Thu, 01 Nov 2001 12:04:57 -0600
To: Mary Thompson , "Thomas W. Fredian"
From: Kate Keahey
Subject: Re: vizapp
Cc: nfc-sc01@fusion.gat.com
Sender: owner-nfc-sc01@fusion.gat.com
Status:
At 09:48 AM 11/1/2001 -0800, Mary Thompson wrote:
>It turns out that we can put off packing natasha off until tommorrow.
>Would this be useful? It sounds like you are putting new versions of the
>software on it for the viz info stuff.
This is up to Tom. He wrote some code enabling instrumentation from the
controller so this will simplify things a lot.
>Kate,
> If you want me to try to install an early version of vizinfo on
>natasha, I will be happy to do so.
Mary, I don't think this code will be available to do anything with
(let alone install ;-) in this timeframe. I will make sure we do as much as
possible to enable a relatively quick install in Denver.
>Mary
>--
>---------------------------------------------------------------------
>Mary R. Thompson
>Distributed Security Research Group (510) 486-7408
>Lawrence Berkeley National Lab http://www-itg.lbl.gov/~mrt
>----------------------------------------------------------------------
__________________________
Dr. Kate Keahey
Math & Computer Science Div.
Argonne National Laboratory
Argonne, IL 60439, USA
(630) 252-1673
===============================================================================
This message was sent to the SciDAC National Fusion Collaboratory (NFC)
workers list nfc-sc01. Visit the Collaboratory at
.
To unsubscribe from this list, please send a message to
majordomo@fusion.gat.com with the following text in the *body* of the
message: unsubscribe nfc-sc01
David P. Schissel:
**************************************************************************
**************************************************************************
X-Authentication-Warning: apollo.gat.com: majordom set sender to
owner-nfc-sc01@fusion.gat.com using -f
X-Sender: keahey@localhost
Date: Thu, 01 Nov 2001 11:55:46 -0600
To: "Thomas W. Fredian"
From: Kate Keahey
Subject: Re: vizapp
Cc: nfc-sc01@fusion.gat.com
Sender: owner-nfc-sc01@fusion.gat.com
Status:
Tom and I just talked on the phone, but in the interest of getting everybody on the same page:
At 12:19 PM 11/1/2001 -0500, Thomas W. Fredian wrote:
>I have NetLogger connections working on a03n, dg0n7 and natasha so far. I've made
>MDSplus functions: NetLoggerOpen(), NetLoggerJobStatus(), NetLoggerTransfer() and
>NetLoggerClose(), for operating the vizapp. Can you make some suggestions on how to
>instrument the demo? Who should be sending the JOB STATUS messages? The controller,
>the efit script and/or the MDSplus servers? Likewise on the TransferPerfTotal
>messages?
Suggestions are in the example.
>What should I put for BW.CURRENT and BW.AVG???? I don't have any good way
>to compute these. What are the units of these anyway?
The idea is to keep them fixed; we don't really need to visualize bandwidth, just
data movement and hopefully the vizapp will visualize at least that. The unit is B/s.
A couple of things I forgot to mention:
1) if the instrumentation is not doable we could "fake" it (as we are doing it now)
by running just this event generator and getting the vizapp to subscribe to events
2) we will be adding a unique "serial number" to both the ID and the FRIENDLY NAME
(different for lbl and anl and different serial number)
If you get the "instrumentation message" and want to do something to help instrument
the demo, please check with Tom, he is on top of it all ;-).
>-tom
>Kate Keahey wrote:
>> Hi,
>>
>> I need help instrumenting the demo with calls to viz app, please read.
>>
>> We are making progress with the application visualizing interactions during
>> the demo to the point where I think it makes sense to instrument the demo.
>> Right now what we mainly see are little red circles appearing in
>> appropriate parts of the country when computation is started, so nothing
>> exciting but it looks like we'll get there. The demo can be instrumented by
>> putting calls reporting on events in the body of demo components when those
>> events happen (so for example when efit writes out data, we report on this
>> event and it will be visualized). There is one problems with instrumenting
>> the demo: unfortunately the Netlogger (which has to be used in order for
>> things to work with this application) does not have a C shell API. I could
>> either write a little program callable from Tom's script or we could push
>> the calls into components for which we do have API. Let me know which you
>> would prefer. I wrote a little program generating events for our demo with
>> lots of comments on how the demo needs to be instrumented (this is the one
>> we use for debugging the app); it is accessible at ~keahey/publish on
>> either the datagrid cluster or sc desksides.
>>
>> Here is how this app works. The interactions are based on a piece of
>> software called Netlogger (see http://www-didc.lbl.gov/NetLogger/). It
>> implements a database where we can post events. Then the vizapp gets the
>> events from there and visualizes them. We need to worry about the first
>> part of the interaction only. Right now and for the next few days the
>> database will be running on terra.mcs.anl.gov reading from port 14835 (see
>> example). At SC it will move to the floor, so it should be configurable.
>>
>> In order to instrument a program, insert calls opening and closing
>> connection to the netlogger at the beginning and end of the program (see
>> example for C API to do this, I will be happy to provide examples in other
>> languages or you can go to the url below). Then insert calls writing events
>> pretty much as they are in the example in the appropriate places (it should
>> be pretty much cut and paste from the example). Compile with netlogger
>> header file and library; on the datagrid cluster and sc desksides the
>> Netlogger installation is in ~keahey/NetLogger-1.6/linux.bin. Mary, I am
>> not sure if you have it on diesel or natasha, installation is essentially
>> just a matter of unpacking. Or I could do it for you if you tell me where.
>>
>> Further info: we are publishing two kinds of events (I took some shortcuts
>> to make things easy so for example bandwidth info is "made up"):
>>
>> 1) JOB_STATUS, format: "ID=%s FRIENDLY.NAME=%s > identifier> JOB.HOST=%s JOBS.SUBMITTED=%d
>> JOBS.COMPLETE=%d JOBS.FAILED=%d BYTES.PRODUCED=%d"
>>
>> 2) "TransferPerfTotal", format: "ID=%s FRIENDLY.NAME=%s> identifier> URL.SOURCE=%s URL.DEST=%s BYTES=%d BW.CURRENT=%f BW.AVG=%f"
>>
>> Here is the help I need:
>>
>> 1) Tom and Qian, since you know best where the event generating things
>> happen in your programs, could you inert the appropriate calls from the
>> example?
>> 2) Mary, could you handle the installation on diesel and natasha?
>>
>> Kate
>>
>> ===============================================================================
>>
>> This message was sent to the SciDAC National Fusion Collaboratory (NFC)
>> workers list nfc-sc01. Visit the Collaboratory at
>> .
>>
>> To unsubscribe from this list, please send a message to
>> majordomo@fusion.gat.com with the following text in the *body* of the
>> message: unsubscribe nfc-sc01
>>
>> David P. Schissel:
__________________________
Dr. Kate Keahey
Math & Computer Science Div.
Argonne National Laboratory
Argonne, IL 60439, USA
(630) 252-1673
===============================================================================
This message was sent to the SciDAC National Fusion Collaboratory (NFC)
workers list nfc-sc01. Visit the Collaboratory at
.
To unsubscribe from this list, please send a message to
majordomo@fusion.gat.com with the following text in the *body* of the
message: unsubscribe nfc-sc01
David P. Schissel:
**************************************************************************
**************************************************************************
X-Authentication-Warning: apollo.gat.com: majordom set sender to
owner-nfc-sc01@fusion.gat.com using -f
Date: Thu, 01 Nov 2001 09:48:34 -0800
From: Mary Thompson
Organization: LBNL
X-Accept-Language: en
To: "Thomas W. Fredian"
CC: Kate Keahey , nfc-sc01@fusion.gat.com
Subject: Re: vizapp
Sender: owner-nfc-sc01@fusion.gat.com
Status:
It turns out that we can put off packing natasha off until tommorrow.
Would this be useful? It sounds like you are putting new versions of the
software on it for the viz info stuff.
Kate,
If you want me to try to install an early version of vizinfo on
natasha, I will be happy to do so.
Mary
--
---------------------------------------------------------------------
Mary R. Thompson
Distributed Security Research Group (510) 486-7408
Lawrence Berkeley National Lab http://www-itg.lbl.gov/~mrt
----------------------------------------------------------------------
===============================================================================
This message was sent to the SciDAC National Fusion Collaboratory (NFC)
workers list nfc-sc01. Visit the Collaboratory at
.
To unsubscribe from this list, please send a message to
majordomo@fusion.gat.com with the following text in the *body* of the
message: unsubscribe nfc-sc01
David P. Schissel:
**************************************************************************
**************************************************************************
X-Authentication-Warning: apollo.gat.com: majordom set sender to
owner-nfc-sc01@fusion.gat.com using -f
X-Sender: keahey@localhost
Date: Thu, 01 Nov 2001 10:20:40 -0600
To: "Thomas W. Fredian"
From: Kate Keahey
Subject: Re: vizapp
Cc: SC01 Demo
Sender: owner-nfc-sc01@fusion.gat.com
Status:
Tom,
the disappearing directory was an nfs problem, like many that we experienced before.
Charles restarted nfs and the contents are back in that directory. Our apologies.
At 10:42 AM 11/1/2001 -0500, Thomas W. Fredian wrote:
>Hi Kate,
>
> I found them on a021 ~keahey/NetLogger-1.6. I think I can call into the
>NetLogger.so dynamically straight from MDSplus so it doesn't look like it will be
>difficult to instrument the demo.
>
>-tom
>
>Kate Keahey wrote:
>
>> Tom,
>>
> my apologies for the wrong paths, I was copying around several accounts,
> fixing right now. The other problem I have no idea about, but trying to
> find out.
>
> At 10:27 AM 11/1/2001 -0500, Thomas W. Fredian wrote:
> >I just started looking into this and just like everything else in this demo
> >preparation, the world changed out from under me. Where might I find the
> >libraries
> >now?
> >
> >dg0n7$ ls ~keahey/NetLogger-1.6/
> >CHANGELOG LICENSE Makefile NLV README README-NLV bin.linux bin.solaris
> >build gnuplot scripts snmp src
> >
> >2 seconds later:
> >
> >dg0n7$ ls ~keahey/NetLogger-1.6/
> >nothing...
> >
> >Your Makefile in a031:~keahey/publisher refers to
> >/nfs/dsl-homes02/keahey/NetLogger-1.6/bin.linux
> >but that directory does not exist either.
> >
> >-tom
> >
> >
> >Kate Keahey wrote:
> >
> > > Hi,
> > >
> > > I need help instrumenting the demo with calls to viz app, please read.
> > >
> > > We are making progress with the application visualizing interactions during
> > > the demo to the point where I think it makes sense to instrument the demo.
> > > Right now what we mainly see are little red circles appearing in
> > > appropriate parts of the country when computation is started, so nothing
> > > exciting but it looks like we'll get there. The demo can be instrumented by
> > > putting calls reporting on events in the body of demo components when those
> > > events happen (so for example when efit writes out data, we report on this
> > > event and it will be visualized). There is one problems with instrumenting
> > > the demo: unfortunately the Netlogger (which has to be used in order for
> > > things to work with this application) does not have a C shell API. I could
> > > either write a little program callable from Tom's script or we could push
> > > the calls into components for which we do have API. Let me know which you
> > > would prefer. I wrote a little program generating events for our demo with
> > > lots of comments on how the demo needs to be instrumented (this is the one
> > > we use for debugging the app); it is accessible at ~keahey/publish on
> > > either the datagrid cluster or sc desksides.
> > >
> > > Here is how this app works. The interactions are based on a piece of
> > > software called Netlogger (see http://www-didc.lbl.gov/NetLogger/). It
> > > implements a database where we can post events. Then the vizapp gets the
> > > events from there and visualizes them. We need to worry about the first
> > > part of the interaction only. Right now and for the next few days the
> > > database will be running on terra.mcs.anl.gov reading from port 14835 (see
> > > example). At SC it will move to the floor, so it should be configurable.
> > >
> > > In order to instrument a program, insert calls opening and closing
> > > connection to the netlogger at the beginning and end of the program (see
> > > example for C API to do this, I will be happy to provide examples in other
> > > languages or you can go to the url below). Then insert calls writing events
> > > pretty much as they are in the example in the appropriate places (it should
> > > be pretty much cut and paste from the example). Compile with netlogger
> > > header file and library; on the datagrid cluster and sc desksides the
> > > Netlogger installation is in ~keahey/NetLogger-1.6/linux.bin. Mary, I am
> > > not sure if you have it on diesel or natasha, installation is essentially
> > > just a matter of unpacking. Or I could do it for you if you tell me where.
> > >
> > > Further info: we are publishing two kinds of events (I took some shortcuts
> > > to make things easy so for example bandwidth info is "made up"):
> > >
> > > 1) JOB_STATUS, format: "ID=%s FRIENDLY.NAME=%s > > identifier> JOB.HOST=%s JOBS.SUBMITTED=%d
> > > JOBS.COMPLETE=%d JOBS.FAILED=%d BYTES.PRODUCED=%d"
> > >
> > > 2) "TransferPerfTotal", format: "ID=%s FRIENDLY.NAME=%s > > identifier> URL.SOURCE=%s URL.DEST=%s BYTES=%d BW.CURRENT=%f BW.AVG=%f"
> > >
> > > Here is the help I need:
> > >
> > > 1) Tom and Qian, since you know best where the event generating things
> > > happen in your programs, could you inert the appropriate calls from the
> > > example?
> > > 2) Mary, could you handle the installation on diesel and natasha?
> > >
> > > Kate
> > >
> > >
> > ===============================================================================
> > >
> > > This message was sent to the SciDAC National Fusion Collaboratory (NFC)
> > > workers list nfc-sc01. Visit the Collaboratory at
> > > .
> > >
> > > To unsubscribe from this list, please send a message to
> > > majordomo@fusion.gat.com with the following text in the *body* of the
> > > message: unsubscribe nfc-sc01
> > >
> > > David P. Schissel:
> >
>
> __________________________
> Dr. Kate Keahey
> Math & Computer Science Div.
> Argonne National Laboratory
> Argonne, IL 60439, USA
> (630) 252-1673
__________________________
Dr. Kate Keahey
Math & Computer Science Div.
Argonne National Laboratory
Argonne, IL 60439, USA
(630) 252-1673
===============================================================================
This message was sent to the SciDAC National Fusion Collaboratory (NFC)
workers list nfc-sc01. Visit the Collaboratory at
.
To unsubscribe from this list, please send a message to
majordomo@fusion.gat.com with the following text in the *body* of the
message: unsubscribe nfc-sc01
David P. Schissel:
**************************************************************************
**************************************************************************
X-Authentication-Warning: apollo.gat.com: majordom set sender to
owner-nfc-sc01@fusion.gat.com using -f
Date: Thu, 01 Nov 2001 10:42:43 -0500
From: "Thomas W. Fredian"
X-Accept-Language: en
To: Kate Keahey
CC: SC01 Demo
Subject: Re: vizapp
Sender: owner-nfc-sc01@fusion.gat.com
Status:
Hi Kate,
I found them on a021 ~keahey/NetLogger-1.6. I think I can call into the
NetLogger.so dynamically straight from MDSplus so it doesn't look like it will be
difficult to instrument the demo.
-tom
Kate Keahey wrote:
> Tom,
>
> my apologies for the wrong paths, I was copying around several accounts,
> fixing right now. The other problem I have no idea about, but trying to
> find out.
>
> At 10:27 AM 11/1/2001 -0500, Thomas W. Fredian wrote:
> >I just started looking into this and just like everything else in this demo
> >preparation, the world changed out from under me. Where might I find the
> >libraries
> >now?
> >
> >dg0n7$ ls ~keahey/NetLogger-1.6/
> >CHANGELOG LICENSE Makefile NLV README README-NLV bin.linux bin.solaris
> >build gnuplot scripts snmp src
> >
> >2 seconds later:
> >
> >dg0n7$ ls ~keahey/NetLogger-1.6/
> >nothing...
> >
> >Your Makefile in a031:~keahey/publisher refers to
> >/nfs/dsl-homes02/keahey/NetLogger-1.6/bin.linux
> >but that directory does not exist either.
> >
> >-tom
> >
> >
> >Kate Keahey wrote:
> >
> > > Hi,
> > >
> > > I need help instrumenting the demo with calls to viz app, please read.
> > >
> > > We are making progress with the application visualizing interactions during
> > > the demo to the point where I think it makes sense to instrument the demo.
> > > Right now what we mainly see are little red circles appearing in
> > > appropriate parts of the country when computation is started, so nothing
> > > exciting but it looks like we'll get there. The demo can be instrumented by
> > > putting calls reporting on events in the body of demo components when those
> > > events happen (so for example when efit writes out data, we report on this
> > > event and it will be visualized). There is one problems with instrumenting
> > > the demo: unfortunately the Netlogger (which has to be used in order for
> > > things to work with this application) does not have a C shell API. I could
> > > either write a little program callable from Tom's script or we could push
> > > the calls into components for which we do have API. Let me know which you
> > > would prefer. I wrote a little program generating events for our demo with
> > > lots of comments on how the demo needs to be instrumented (this is the one
> > > we use for debugging the app); it is accessible at ~keahey/publish on
> > > either the datagrid cluster or sc desksides.
> > >
> > > Here is how this app works. The interactions are based on a piece of
> > > software called Netlogger (see http://www-didc.lbl.gov/NetLogger/). It
> > > implements a database where we can post events. Then the vizapp gets the
> > > events from there and visualizes them. We need to worry about the first
> > > part of the interaction only. Right now and for the next few days the
> > > database will be running on terra.mcs.anl.gov reading from port 14835 (see
> > > example). At SC it will move to the floor, so it should be configurable.
> > >
> > > In order to instrument a program, insert calls opening and closing
> > > connection to the netlogger at the beginning and end of the program (see
> > > example for C API to do this, I will be happy to provide examples in other
> > > languages or you can go to the url below). Then insert calls writing events
> > > pretty much as they are in the example in the appropriate places (it should
> > > be pretty much cut and paste from the example). Compile with netlogger
> > > header file and library; on the datagrid cluster and sc desksides the
> > > Netlogger installation is in ~keahey/NetLogger-1.6/linux.bin. Mary, I am
> > > not sure if you have it on diesel or natasha, installation is essentially
> > > just a matter of unpacking. Or I could do it for you if you tell me where.
> > >
> > > Further info: we are publishing two kinds of events (I took some shortcuts
> > > to make things easy so for example bandwidth info is "made up"):
> > >
> > > 1) JOB_STATUS, format: "ID=%s FRIENDLY.NAME=%s > > identifier> JOB.HOST=%s JOBS.SUBMITTED=%d
> > > JOBS.COMPLETE=%d JOBS.FAILED=%d BYTES.PRODUCED=%d"
> > >
> > > 2) "TransferPerfTotal", format: "ID=%s FRIENDLY.NAME=%s > > identifier> URL.SOURCE=%s URL.DEST=%s BYTES=%d BW.CURRENT=%f BW.AVG=%f"
> > >
> > > Here is the help I need:
> > >
> > > 1) Tom and Qian, since you know best where the event generating things
> > > happen in your programs, could you inert the appropriate calls from the
> > > example?
> > > 2) Mary, could you handle the installation on diesel and natasha?
> > >
> > > Kate
> > >
> > >
> > ===============================================================================
> > >
> > > This message was sent to the SciDAC National Fusion Collaboratory (NFC)
> > > workers list nfc-sc01. Visit the Collaboratory at
> > > .
> > >
> > > To unsubscribe from this list, please send a message to
> > > majordomo@fusion.gat.com with the following text in the *body* of the
> > > message: unsubscribe nfc-sc01
> > >
> > > David P. Schissel:
> >
>
> __________________________
> Dr. Kate Keahey
> Math & Computer Science Div.
> Argonne National Laboratory
> Argonne, IL 60439, USA
> (630) 252-1673
===============================================================================
This message was sent to the SciDAC National Fusion Collaboratory (NFC)
workers list nfc-sc01. Visit the Collaboratory at
.
To unsubscribe from this list, please send a message to
majordomo@fusion.gat.com with the following text in the *body* of the
message: unsubscribe nfc-sc01
David P. Schissel:
**************************************************************************
**************************************************************************
X-Authentication-Warning: apollo.gat.com: majordom set sender
to owner-nfc-sc01@fusion.gat.com using -f
X-Sender: keahey@localhost
Date: Thu, 01 Nov 2001 09:38:09 -0600
To: "Thomas W. Fredian"
From: Kate Keahey
Subject: Re: vizapp
Cc: nfc-sc01@fusion.gat.com
Sender: owner-nfc-sc01@fusion.gat.com
Status:
Tom,
my apologies for the wrong paths, I was copying around several accounts, fixing right
now. The other problem I have no idea about, but trying to find out.
At 10:27 AM 11/1/2001 -0500, Thomas W. Fredian wrote:
>I just started looking into this and just like everything else in this demo
>preparation, the world changed out from under me. Where might I find the libraries
>now?
>
>dg0n7$ ls ~keahey/NetLogger-1.6/
>CHANGELOG LICENSE Makefile NLV README README-NLV bin.linux bin.solaris
>build gnuplot scripts snmp src
>
>2 seconds later:
>
>dg0n7$ ls ~keahey/NetLogger-1.6/
>nothing...
>
>Your Makefile in a031:~keahey/publisher refers to
>/nfs/dsl-homes02/keahey/NetLogger-1.6/bin.linux
>but that directory does not exist either.
>
>-tom
>
>
>Kate Keahey wrote:
>
>> Hi,
>>
>> I need help instrumenting the demo with calls to viz app, please read.
>>
>> We are making progress with the application visualizing interactions during
>> the demo to the point where I think it makes sense to instrument the demo.
> Right now what we mainly see are little red circles appearing in
> appropriate parts of the country when computation is started, so nothing
> exciting but it looks like we'll get there. The demo can be instrumented by
> putting calls reporting on events in the body of demo components when those
> events happen (so for example when efit writes out data, we report on this
> event and it will be visualized). There is one problems with instrumenting
> the demo: unfortunately the Netlogger (which has to be used in order for
> things to work with this application) does not have a C shell API. I could
> either write a little program callable from Tom's script or we could push
> the calls into components for which we do have API. Let me know which you
> would prefer. I wrote a little program generating events for our demo with
> lots of comments on how the demo needs to be instrumented (this is the one
> we use for debugging the app); it is accessible at ~keahey/publish on
> either the datagrid cluster or sc desksides.
>
> Here is how this app works. The interactions are based on a piece of
> software called Netlogger (see http://www-didc.lbl.gov/NetLogger/). It
> implements a database where we can post events. Then the vizapp gets the
> events from there and visualizes them. We need to worry about the first
> part of the interaction only. Right now and for the next few days the
> database will be running on terra.mcs.anl.gov reading from port 14835 (see
> example). At SC it will move to the floor, so it should be configurable.
>
> In order to instrument a program, insert calls opening and closing
> connection to the netlogger at the beginning and end of the program (see
> example for C API to do this, I will be happy to provide examples in other
> languages or you can go to the url below). Then insert calls writing events
> pretty much as they are in the example in the appropriate places (it should
> be pretty much cut and paste from the example). Compile with netlogger
> header file and library; on the datagrid cluster and sc desksides the
> Netlogger installation is in ~keahey/NetLogger-1.6/linux.bin. Mary, I am
> not sure if you have it on diesel or natasha, installation is essentially
> just a matter of unpacking. Or I could do it for you if you tell me where.
>
> Further info: we are publishing two kinds of events (I took some shortcuts
> to make things easy so for example bandwidth info is "made up"):
>
> 1) JOB_STATUS, format: "ID=%s FRIENDLY.NAME=%s identifier> JOB.HOST=%s JOBS.SUBMITTED=%d
> JOBS.COMPLETE=%d JOBS.FAILED=%d BYTES.PRODUCED=%d"
>
> 2) "TransferPerfTotal", format: "ID=%s FRIENDLY.NAME=%s identifier> URL.SOURCE=%s URL.DEST=%s BYTES=%d BW.CURRENT=%f BW.AVG=%f"
>
> Here is the help I need:
>
> 1) Tom and Qian, since you know best where the event generating things
> happen in your programs, could you inert the appropriate calls from the
> example?
> 2) Mary, could you handle the installation on diesel and natasha?
>
> Kate
>
> ===============================================================================
>
> This message was sent to the SciDAC National Fusion Collaboratory (NFC)
> workers list nfc-sc01. Visit the Collaboratory at
> .
>
> To unsubscribe from this list, please send a message to
> majordomo@fusion.gat.com with the following text in the *body* of the
> message: unsubscribe nfc-sc01
>
> David P. Schissel:
__________________________
Dr. Kate Keahey
Math & Computer Science Div.
Argonne National Laboratory
Argonne, IL 60439, USA
(630) 252-1673
===============================================================================
This message was sent to the SciDAC National Fusion Collaboratory (NFC)
workers list nfc-sc01. Visit the Collaboratory at
.
To unsubscribe from this list, please send a message to
majordomo@fusion.gat.com with the following text in the *body* of the
message: unsubscribe nfc-sc01
David P. Schissel:
**************************************************************************
**************************************************************************
X-Authentication-Warning: apollo.gat.com: majordom set sender to
owner-nfc-sc01@fusion.gat.com using -f
Date: Thu, 01 Nov 2001 10:27:22 -0500
From: "Thomas W. Fredian"
X-Accept-Language: en
To: Kate Keahey
CC: nfc-sc01@fusion.gat.com
Subject: Re: vizapp
Sender: owner-nfc-sc01@fusion.gat.com
Status:
I just started looking into this and just like everything else in this demo
preparation, the world changed out from under me. Where might I find the libraries
now?
dg0n7$ ls ~keahey/NetLogger-1.6/
CHANGELOG LICENSE Makefile NLV README README-NLV bin.linux bin.solaris
build gnuplot scripts snmp src
2 seconds later:
dg0n7$ ls ~keahey/NetLogger-1.6/
nothing...
Your Makefile in a031:~keahey/publisher refers to
/nfs/dsl-homes02/keahey/NetLogger-1.6/bin.linux
but that directory does not exist either.
-tom
Kate Keahey wrote:
> Hi,
>
> I need help instrumenting the demo with calls to viz app, please read.
>
> We are making progress with the application visualizing interactions during
> the demo to the point where I think it makes sense to instrument the demo.
> Right now what we mainly see are little red circles appearing in
> appropriate parts of the country when computation is started, so nothing
> exciting but it looks like we'll get there. The demo can be instrumented by
> putting calls reporting on events in the body of demo components when those
> events happen (so for example when efit writes out data, we report on this
> event and it will be visualized). There is one problems with instrumenting
> the demo: unfortunately the Netlogger (which has to be used in order for
> things to work with this application) does not have a C shell API. I could
> either write a little program callable from Tom's script or we could push
> the calls into components for which we do have API. Let me know which you
> would prefer. I wrote a little program generating events for our demo with
> lots of comments on how the demo needs to be instrumented (this is the one
> we use for debugging the app); it is accessible at ~keahey/publish on
> either the datagrid cluster or sc desksides.
>
> Here is how this app works. The interactions are based on a piece of
> software called Netlogger (see http://www-didc.lbl.gov/NetLogger/). It
> implements a database where we can post events. Then the vizapp gets the
> events from there and visualizes them. We need to worry about the first
> part of the interaction only. Right now and for the next few days the
> database will be running on terra.mcs.anl.gov reading from port 14835 (see
> example). At SC it will move to the floor, so it should be configurable.
>
> In order to instrument a program, insert calls opening and closing
> connection to the netlogger at the beginning and end of the program (see
> example for C API to do this, I will be happy to provide examples in other
> languages or you can go to the url below). Then insert calls writing events
> pretty much as they are in the example in the appropriate places (it should
> be pretty much cut and paste from the example). Compile with netlogger
> header file and library; on the datagrid cluster and sc desksides the
> Netlogger installation is in ~keahey/NetLogger-1.6/linux.bin. Mary, I am
> not sure if you have it on diesel or natasha, installation is essentially
> just a matter of unpacking. Or I could do it for you if you tell me where.
>
> Further info: we are publishing two kinds of events (I took some shortcuts
> to make things easy so for example bandwidth info is "made up"):
>
> 1) JOB_STATUS, format: "ID=%s FRIENDLY.NAME=%s identifier> JOB.HOST=%s JOBS.SUBMITTED=%d
> JOBS.COMPLETE=%d JOBS.FAILED=%d BYTES.PRODUCED=%d"
>
> 2) "TransferPerfTotal", format: "ID=%s FRIENDLY.NAME=%s identifier> URL.SOURCE=%s URL.DEST=%s BYTES=%d BW.CURRENT=%f BW.AVG=%f"
>
> Here is the help I need:
>
> 1) Tom and Qian, since you know best where the event generating things
> happen in your programs, could you inert the appropriate calls from the
> example?
> 2) Mary, could you handle the installation on diesel and natasha?
>
> Kate
>
> ===============================================================================
>
> This message was sent to the SciDAC National Fusion Collaboratory (NFC)
> workers list nfc-sc01. Visit the Collaboratory at
> .
>
> To unsubscribe from this list, please send a message to
> majordomo@fusion.gat.com with the following text in the *body* of the
> message: unsubscribe nfc-sc01
>
> David P. Schissel:
===============================================================================
This message was sent to the SciDAC National Fusion Collaboratory (NFC)
workers list nfc-sc01. Visit the Collaboratory at
.
To unsubscribe from this list, please send a message to
majordomo@fusion.gat.com with the following text in the *body* of the
message: unsubscribe nfc-sc01
David P. Schissel:
**************************************************************************
**************************************************************************
