It's just kinda standard. Just like you can specify different c/c++ compilers
and flags, you can do the same with f77/f90.
-Ben
On May 31, 2013, at 4:46 PM, "Subramanya Sadasiva"
mailto:ssada...@purdue.edu>> wrote:
Hi Ben,
I did that , and things are building. Thanks!
Is there a particular rea
Hi Ben,
I did that , and things are building. Thanks!
Is there a particular reason to have F77 and F handled through separate
compilers?
Subramanya
Subramanya G Sadasiva,
Graduate Research Assistant,
Hierarchical Design and Characterization Laboratory,
School of Mechanical Engineering,
Purdue Uni
Hi ,
I get the following error while trying to run make on the main git version.
PPF77forbind/src/libdbg_la-addrwrap.lo
../../../../libtool: line 1122: no: command not found
make[2]: *** [forbind/src/libdbg_la-addrwrap.lo] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all-recursive
On May 31, 2013, at 4:25 PM, Subramanya Sadasiva wrote:
> PPF77forbind/src/libdbg_la-addrwrap.lo
> ../../../../libtool: line 1122: no: command not found
> make[2]: *** [forbind/src/libdbg_la-addrwrap.lo] Error 1
> make[1]: *** [all-recursive] Error 1
> make: *** [all-recursive] Error 1
>
>
On May 31, 2013, at 11:45 AM, Cody Permann wrote:
>
>
>
> On Fri, May 31, 2013 at 9:39 AM, Manav Bhatia wrote:
>
>
>
>
> On May 31, 2013, at 11:27 AM, Cody Permann wrote:
>
> > The nice thing is that you can return to your big memory machine when you
> > are through to perform visu
On Fri, May 31, 2013 at 9:39 AM, Manav Bhatia wrote:
>
>
>
>
> On May 31, 2013, at 11:27 AM, Cody Permann wrote:
>
> > The nice thing is that you can return to your big memory machine when
> you are through to perform visualization. Paraview and other viz packages
> will automatically read all
On Fri, 31 May 2013, Cody Permann wrote:
> On Fri, May 31, 2013 at 9:08 AM, Manav Bhatia wrote:
>
>> Correct? Following the initial read, if I intend to re-partition the
>> (ParallelMesh) mesh object with Parmetis and redistribute the elements,
>> would the data-structure support it?
>
> I belie
On May 31, 2013, at 11:27 AM, Cody Permann wrote:
> The nice thing is that you can return to your big memory machine when you are
> through to perform visualization. Paraview and other viz packages will
> automatically read all of the output files at once and piece the final result
> into
On Fri, May 31, 2013 at 9:08 AM, Manav Bhatia wrote:
> On Thu, May 30, 2013 at 5:50 PM, Kirk, Benjamin (JSC-EG311) <
> benjamin.kir...@nasa.gov> wrote:
>
> > On May 30, 2013, at 4:44 PM, "Manav Bhatia"
> wrote:
> >
> > > At this stage, should I attempt to read the .xdr file into my code with
> >
On Thu, May 30, 2013 at 5:50 PM, Kirk, Benjamin (JSC-EG311) <
benjamin.kir...@nasa.gov> wrote:
> On May 30, 2013, at 4:44 PM, "Manav Bhatia" wrote:
>
> > At this stage, should I attempt to read the .xdr file into my code with
> a ParallelMesh data structure? Would the mesh from this .xdr file be
Thanks for the infos.
I guess that the savings I was reporting were also due to the DofObjects
refactoring.
Do you store one DofObject per VariableGroup?
I guess in my usage pattern one DofObject per element would be the most
efficient strategy.
Would it be hard to do such a thing?
I think that to
11 matches
Mail list logo
