random. This is mandatory for some of our systems.
Alan
-Original Message-
From: Utkarsh Ayachit [mailto:utkarsh.ayac...@kitware.com]
Sent: Monday, January 11, 2010 12:05 PM
To: Moreland, Kenneth
Cc: Rick Angelini; Scott, W Alan; ParaView
Subje
> >>> >>> >> >> Sent: Monday, January 11, 2010 12:05 PM
>> >>> >>> >> >> To: Moreland, Kenneth
>> >>> >>> >> >> Cc: Rick Angelini; Scott, W Alan; ParaView
>> >>> >>> >> >> Subject: R
ROJECTNUM=XYZ789Project
>>> >>
>>> >> Where "hostname" is the Server name from the .pvsc file.
>>> >>
>>> >>
>>> >> Utkarsh Ayachit wrote:
>>> >>>
>>> >>> I've ensured that whe
ame2.PROJECTNUM=XYZ789Project
>>> >>
>>> >> Where "hostname" is the Server name from the .pvsc file.
>>> >>
>>> >>
>>> >> Utkarsh Ayachit wrote:
>>> >>>
>>> >>> I've ensured that w
gt; I've ensured that when "random" is specified as the default value for
>> >>> any option, which is the case with --connect-id, then the value is
>> >>> always regenerated, so this will be a non-issue. Also you can always
>> >>> add save="
d flag
>>> > between sessions? This needs to be new, and random, each and
every time we
>>> > run.
>>> >
>>> > This was the reason that the save option was put into Paraview -
so we
>>> > wouldn't save the --connect-id variable
nuary 11, 2010 1:52 PM
To: Scott, W Alan; Utkarsh Ayachit
Cc: Rick Angelini; ParaView
Subject: Re: [Paraview] Paraview 3.6.x connection definition files
Utkarsh,
Is there a reason why we should not save all options as
opposed to just those with the "save" attribute? I cannot
think of a good
t;>> case.
>>>
>>> Utkarsh
>>>
>>> On Mon, Jan 11, 2010 at 8:38 PM, Scott, W Alan wrote:
>>> > Am I missing something, or would we also save the --connect-id flag
>>> > between sessions? This needs to be new, and random, each and every time
>&g
connection definitions files, so you need to maintain the
>> >> >>> functionality of item #2 & item #4. Maybe there's a check
>> >> >> to make sure
>> >> >>> that the user-defined connection is not the same name as
>> >&g
: Moreland, Kenneth
>> Sent: Monday, January 11, 2010 1:52 PM
>> To: Scott, W Alan; Utkarsh Ayachit
>> Cc: Rick Angelini; ParaView
>> Subject: Re: [Paraview] Paraview 3.6.x connection definition files
>>
>> Utkarsh,
>>
>> Is there a reason why we sh
Excellent.
Alan
> -Original Message-
> From: Utkarsh Ayachit [mailto:utkarsh.ayac...@kitware.com]
> Sent: Tuesday, January 12, 2010 7:37 AM
> To: Scott, W Alan
> Cc: Moreland, Kenneth; Rick Angelini; ParaView
> Subject: Re: [Paraview] Paraview 3.6.x connection definit
Paraview - so we
> wouldn't save the --connect-id variable.
>
> Alan
>
>> -Original Message-
>> From: Moreland, Kenneth
>> Sent: Monday, January 11, 2010 1:52 PM
>> To: Scott, W Alan; Utkarsh Ayachit
>> Cc: Rick Angelini; ParaView
>> Subject:
Message-
> From: Moreland, Kenneth
> Sent: Monday, January 11, 2010 1:52 PM
> To: Scott, W Alan; Utkarsh Ayachit
> Cc: Rick Angelini; ParaView
> Subject: Re: [Paraview] Paraview 3.6.x connection definition files
>
> Utkarsh,
>
> Is there a reason why we should not sa
not be saved between sessions - and to truly be random. This is
>> mandatory for some of our systems.
>>
>> Alan
>>
>>> -Original Message-
>>> From: Utkarsh Ayachit [mailto:utkarsh.ayac...@kitware.com]
>>> Sent: Monday, January 11, 2010 12:05 PM
>&g
re.com]
>> Sent: Monday, January 11, 2010 12:05 PM
>> To: Moreland, Kenneth
>> Cc: Rick Angelini; Scott, W Alan; ParaView
>> Subject: Re: [Paraview] Paraview 3.6.x connection definition files
>>
>> Folks,
>>
>> I've committed a fix for this. The
tkarsh.ayac...@kitware.com]
> Sent: Monday, January 11, 2010 12:05 PM
> To: Moreland, Kenneth
> Cc: Rick Angelini; Scott, W Alan; ParaView
> Subject: Re: [Paraview] Paraview 3.6.x connection definition files
>
> Folks,
>
> I've committed a fix for this. The updating of th
default_server.pvsc file.
>> > * Upon rerunning ParaView, the wrong information was picked
>> up from
>> > the servers.pvsc file.
>> >
>> >
>> > What would be the correct behavior? We want to always use
> we even need this?)
> * Write preferences into a preferences file.
> Thoughts?
> Alan
>
>
> *From:* Moreland, Kenneth
> *Sent:* Thursday, November 05, 2009 8:02 AM
> *To:* Rick Angelini; Scott, W Alan
> *Cc:* ParaView
> *Subject:* Re: [Para
into a preferences file.
Thoughts?
Alan
*From:* Moreland, Kenneth
*Sent:* Thursday, November 05, 2009 8:02 AM
*To:* Rick Angelini; Scott, W Alan
*Cc:* ParaView
*Subject:* Re: [Paraview] Paraview 3.6.x connection definit
ed Message
*From: *Rick Angelini
*Date: *Fri, 23 Oct 2009 10:55:10 -0600
*To: *
*Subject: *[Paraview] Paraview 3.6.x connection definition files
I have questions regarding the use of connection definition files.
I have created numerous connection definition files for
call if you want to discuss.
Alan
-- Forwarded Message
From: Rick Angelini
Date: Fri, 23 Oct 2009 10:55:10 -0600
To:
Subject: [Paraview] Paraview 3.6.x connection definition files
I have questions regarding the use of connection definition files.
I have created numerous connection defin
That's interesting. Let me take a look at this. The goal of
default_servers.pvsc was indeed to support the use-case as you
describe, where the site-administrator can change the configuration
file and all the "users" get the updated configuration. Since this
code passed through many hands, there may
I have questions regarding the use of connection definition files.
I have created numerous connection definition files for various clusters
and compute systems that we have here. Up until now, I've been
distributing those pvsc files through a common directory that all of my
users have ac
23 matches
Mail list logo
