[prev in list] [next in list] [prev in thread] [next in thread]
List: paraview
Subject: Re: [Paraview] Issue with Catalyst spack package
From: "Dorier, Matthieu" <mdorier () anl ! gov>
Date: 2018-09-12 21:19:58
Message-ID: SN6PR09MB2862AC3627DB99B72097C473A31B0 () SN6PR09MB2862 ! namprd09 ! prod ! outlook ! com
[Download RAW message or body]
Hi,
I was wondering if there has been any development in this issue since July?
We will soon provide a Spack package for Damaris. Damaris now supports Catalyst as an \
in-situ visualization backend, so it would be great to be able to support \
Damaris+Catalyst through Spack.
Thanks!
Matthieu
________________________________
From: Mark Olesen <Mark.Olesen@esi-group.com>
Sent: Thursday, July 5, 2018 11:07:27 AM
To: Dorier, Matthieu; paraview@public.kitware.com
Subject: Re: [Paraview] Issue with Catalyst spack package
Yes this is something that Simone has been trying to tackle:
https://github.com/RemoteConnectionManager/spack/commits/packages/update_paraview
You can try a few different things, but nothing really helps.
In the spack package it might help to set the GIT_DIR env to point to
the catalyst directory before the patch/staging part, but that might
just prevent the warning about exploring across file boundaries.
On top of that someone (Andy!) probably needs to adjust the catalyze.py
script to add the checks there, since this error will always occur when
building from a tarball.
/mark
On 07/05/18 11:23, Dorier, Matthieu wrote:
> Hi,
>
>
> I've been trying to install Catalyst using Spack, but ran into an issue
> that I think is caused by Catalyst (some python script in the ParaView
> source tree trying to use git on a directory that isn't managed by git).
> At least that's my first guess...
>
>
> Here is the full issue described on the Spack google group:
>
> https://groups.google.com/forum/#!topic/spack/Pzn3C7KrF7w
>
>
> Thanks,
>
>
> Matthieu
>
>
>
> _______________________________________________
> Powered by www.kitware.com<http://www.kitware.com>
>
> ParaView discussion is moving! Please visit https://discourse.paraview.org/ for \
> future posts.
> Visit other Kitware open-source projects at \
> http://www.kitware.com/opensource/opensource.html
> Please keep messages on-topic and check the ParaView Wiki at: \
> http://paraview.org/Wiki/ParaView
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> https://public.kitware.com/mailman/listinfo/paraview
>
--
Dr Mark OLESEN
Principal Engineer, ESI-OpenCFD
ESI GmbH | Einsteinring 24 | 85609 Munich | GERMANY
Mob. +49 171 9710 149
www.openfoam.com<http://www.openfoam.com> | \
www.esi-group.com<http://www.esi-group.com> | mark.olesen@esi-group.com
[Attachment #3 (text/html)]
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<style type="text/css" style="display:none;"><!-- P {margin-top:0;margin-bottom:0;} \
--></style> </head>
<body dir="ltr">
<div id="divtagdefaultwrapper" \
style="font-size:10pt;color:#333399;font-family:Tahoma,Geneva,sans-serif;" dir="ltr"> \
<p style="margin-top:0;margin-bottom:0">Hi,</p> <p \
style="margin-top:0;margin-bottom:0"><br> </p>
<p style="margin-top:0;margin-bottom:0">I was wondering if there has been any \
development in this issue since July?</p> <p \
style="margin-top:0;margin-bottom:0"><br> </p>
<p style="margin-top:0;margin-bottom:0">We will soon provide a Spack package for \
Damaris. Damaris now supports Catalyst as an in-situ visualization backend, so it \
would be great to be able to support Damaris+Catalyst through Spack.</p> <p \
style="margin-top:0;margin-bottom:0"><br> </p>
<p style="margin-top:0;margin-bottom:0">Thanks!</p>
<p style="margin-top:0;margin-bottom:0"><br>
</p>
<p style="margin-top:0;margin-bottom:0">Matthieu<br>
</p>
</div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" \
style="font-size:11pt" color="#000000"><b>From:</b> Mark Olesen \
<Mark.Olesen@esi-group.com><br> <b>Sent:</b> Thursday, July 5, 2018 11:07:27 \
AM<br> <b>To:</b> Dorier, Matthieu; paraview@public.kitware.com<br>
<b>Subject:</b> Re: [Paraview] Issue with Catalyst spack package</font>
<div> </div>
</div>
<div class="BodyFragment"><font size="2"><span style="font-size:11pt;">
<div class="PlainText">Yes this is something that Simone has been trying to \
tackle:<br> <br>
<a href="https://github.com/RemoteConnectionManager/spack/commits/packages/update_para \
view">https://github.com/RemoteConnectionManager/spack/commits/packages/update_paraview</a><br>
<br>
You can try a few different things, but nothing really helps.<br>
In the spack package it might help to set the GIT_DIR env to point to <br>
the catalyst directory before the patch/staging part, but that might <br>
just prevent the warning about exploring across file boundaries.<br>
<br>
On top of that someone (Andy!) probably needs to adjust the catalyze.py <br>
script to add the checks there, since this error will always occur when <br>
building from a tarball.<br>
<br>
/mark<br>
<br>
<br>
On 07/05/18 11:23, Dorier, Matthieu wrote:<br>
> Hi,<br>
> <br>
> <br>
> I've been trying to install Catalyst using Spack, but ran into an issue <br>
> that I think is caused by Catalyst (some python script in the ParaView <br>
> source tree trying to use git on a directory that isn't managed by git). <br>
> At least that's my first guess...<br>
> <br>
> <br>
> Here is the full issue described on the Spack google group:<br>
> <br>
> <a href="https://groups.google.com/forum/#!topic/spack/Pzn3C7KrF7w">https://groups.google.com/forum/#!topic/spack/Pzn3C7KrF7w</a><br>
> <br>
> <br>
> Thanks,<br>
> <br>
> <br>
> Matthieu<br>
> <br>
> <br>
> <br>
> _______________________________________________<br>
> Powered by <a href="http://www.kitware.com">www.kitware.com</a><br>
> <br>
> ParaView discussion is moving! Please visit <a \
href="https://discourse.paraview.org/"> https://discourse.paraview.org/</a> for \
future posts.<br> > <br>
> Visit other Kitware open-source projects at <a \
href="http://www.kitware.com/opensource/opensource.html"> \
http://www.kitware.com/opensource/opensource.html</a><br> > <br>
> Please keep messages on-topic and check the ParaView Wiki at: <a \
href="http://paraview.org/Wiki/ParaView"> http://paraview.org/Wiki/ParaView</a><br>
> <br>
> Search the list archives at: <a \
href="http://markmail.org/search/?q=ParaView">http://markmail.org/search/?q=ParaView</a><br>
> <br>
> Follow this link to subscribe/unsubscribe:<br>
> <a href="https://public.kitware.com/mailman/listinfo/paraview">https://public.kitware.com/mailman/listinfo/paraview</a><br>
> <br>
<br>
-- <br>
Dr Mark OLESEN<br>
Principal Engineer, ESI-OpenCFD<br>
ESI GmbH | Einsteinring 24 | 85609 Munich | GERMANY<br>
Mob. +49 171 9710 149<br>
<a href="http://www.openfoam.com">www.openfoam.com</a> | <a \
href="http://www.esi-group.com"> www.esi-group.com</a> | \
mark.olesen@esi-group.com<br> </div>
</span></font></div>
</body>
</html>
_______________________________________________
Powered by www.kitware.com
ParaView discussion is moving! Please visit https://discourse.paraview.org/ for future posts.
Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView
Search the list archives at: http://markmail.org/search/?q=ParaView
Follow this link to subscribe/unsubscribe:
https://public.kitware.com/mailman/listinfo/paraview
--===============1680072955==--
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic