[visit-developers] NOTICE: NEW TELECON NUMBER

Meredith, Jeremy S. jsmeredith at ornl.gov
Fri May 15 17:05:24 EDT 2009


Howdy, folks!

Please use this access information instead:

Phone:    866-812-9258
Passcode: 4313222



--
Jeremy Meredith
Oak Ridge National Laboratory


> -----Original Message-----
> From: Meredith, Jeremy S.
> Sent: Friday, May 15, 2009 4:03 PM
> To: VisIt Developers
> Subject: NOTICE: pay attention for new telecon number
> Importance: High
> 
> Hi, folks.  It's been suggested the VACET project gets charged when we
> use the line, so I'm investigating options.  I'll let you know when I
> get this nailed down, but the point is:
> 
> Pay attention to this mailing list before the teleconference on Monday
> to see if I've sent a new number/passcode.
> 
> Thanks!
> 
> --
> Jeremy Meredith
> Oak Ridge National Laboratory
> 
> 
> > -----Original Message-----
> > From: Meredith, Jeremy S. [mailto:jsmeredith at ornl.gov]
> > Sent: Thursday, May 14, 2009 6:26 PM
> > To: VisIt Developers
> > Subject: [visit-developers] 2.0 agenda for Mon, May 18
> >
> > Greetings, all!
> >
> > I haven't heard from quite everyone I think plans to join, but we're
> > close, so I'm going to proceed.  First, since our chosen time
> virtually
> > overlaps with an on-hiatus VACET SEG telecon, it should be perfectly
> > safe to use that line, especially since the purpose is related.  Any
> > concerns, let me know and I'll find us a different one.
> >
> > Date    : Monday, May 18
> > Time    : 11am Pacific / 2pm Eastern
> > Number  : 866-796-5063
> > Passcode: 173532
> > Agenda  :
> >
> > This week, we'll be discussing what I'll call a "major component
> > overhaul".
> >
> > Some topics in this area:
> > * are there reasons to merge address spaces?
> >   - e.g. combine the viewer and gui to make interaction better, or
> > enable MDI
> >   - and if there's a reason, can we do it?
> > * any major communication patterns we need to re-think?
> >   - e.g. GUI no longer talks to mdserver
> >   - e.g. engine talks on stdin/out to support highly restrictive
> > environments
> > * could we distill the engine to a standalone library
> >   - e.g. good for in-situ in non-dynamic-loading environments
> >   - or as a standalone analysis library
> >
> > Bring your ideas and thinking caps -- this one's not an easy place to
> > start.  :-)
> >
> > --
> > Jeremy Meredith
> > Oak Ridge National Laboratory



More information about the visit-developers mailing list