<html dir="ltr"><head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<style>@page Section1 {margin: 1.0in 1.25in 1.0in 1.25in; }
P.MsoNormal {
        FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
LI.MsoNormal {
        FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
DIV.MsoNormal {
        FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
A:link {
        COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
        COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
        COLOR: purple; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
        COLOR: purple; TEXT-DECORATION: underline
}
SPAN.EmailStyle17 {
        COLOR: windowtext; FONT-FAMILY: Arial
}
DIV.Section1 {
        
}
</style>
<meta content="MSHTML 6.00.6000.16674" name="GENERATOR">
<style title="owaParaStyle">P {
        MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
</style>
</head>
<body lang="EN-US" vlink="purple" link="blue" ocsi="x">
<div dir="ltr"><font face="Courier New" color="#000000" size="2">The underlying stream tracer has the ability to take a second data set to use as the initial seed points for the tracing of the stream lines. I think it is possible (and perhaps one of the Kitware
gurus can back me up on this) that it should be straightforward to create some XML filter specification that you can plug in to expose the stream tracer as a two-input filter.</font></div>
<div dir="ltr"><font face="courier new" size="2"></font> </div>
<div dir="ltr"><font face="courier new" size="2">This, of course, is all assuming that you can specify your domain inlets as its own data set. However, I can think of no easier way to specify them.</font></div>
<div dir="ltr"><font face="courier new" size="2"></font> </div>
<div dir="ltr"><font face="courier new" size="2">-Ken</font></div>
<div dir="ltr"><font face="courier new" size="2"></font> </div>
<div id="divRpF316144" style="DIRECTION: ltr">
<hr tabindex="-1">
<font face="Tahoma" size="2"><b>From:</b> paraview-bounces@paraview.org [paraview-bounces@paraview.org] On Behalf Of Alexej Goehring [Alexej.Goehring@arup.com]<br>
<b>Sent:</b> Monday, July 21, 2008 3:34 PM<br>
<b>To:</b> paraview@paraview.org<br>
<b>Subject:</b> [Paraview] Streamlines from boundary/part values<br>
</font><br>
</div>
<div></div>
<div>
<div class="Section1">
<p class="MsoNormal"><font face="Arial" size="2"><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">Hi there,</span></font></p>
<p class="MsoNormal"><font face="Arial" size="2"><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"></span></font> </p>
<p class="MsoNormal"><font face="Arial" size="2"><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">I’m a newbie and investigation the feasibility of using paraview in the office. One of our current tasks is to show streamlines origination from domain inlets
and I was wondering whether there’s an easy way of doing so? Creating a line or a point is a bit tedious.</span></font></p>
<p class="MsoNormal"><font face="Arial" size="2"><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"></span></font> </p>
<p class="MsoNormal"><font face="Arial" size="2"><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">Thanks,</span></font></p>
<p class="MsoNormal"><font face="Arial" size="2"><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"></span></font> </p>
<p class="MsoNormal"><font face="Arial" size="2"><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">Alexej</span></font></p>
<p class="MsoNormal"><font face="Arial" size="2"><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"></span></font> </p>
</div>
<pre>____________________________________________________________
Electronic mail messages entering and leaving Arup business
systems are scanned for acceptability of content and viruses
</pre>
</div>
</body>
</html>