CU Boulder Computer Science has an immediate opening for a postdoctoral
researcher in the development of robust and efficient methods for high
order/compatible PDE discretization and multilevel solvers, including
deployment in open source libraries. The project is especially
interested in
Run in the debugger and step/next through the code to see what code path it
is taking and why it doesn't seem to follow the intended code path.
> On Mar 26, 2018, at 7:10 AM, Matthew Knepley wrote:
>
> On Mon, Mar 26, 2018 at 1:15 AM, TAY wee-beng
Unfortunately due to a "feature" of Fortran you can no longer store PETSc
objects in common blocks; you can use modules, for example, if you need to
access the objects from multiple routines without passing them as arguments.
Barry
We changed our examples to reflect this problem.
In upgrading to PETSc v3.8.x, we are seeing a compilation error with
gfortran (version 6.2.0, users report the same problem with version
7.x). The compile error is thrown when, say, type KSP variables are
put in common blocks; we do not see any errors with this construct
when using ifort
On Mon, Mar 26, 2018 at 1:15 AM, TAY wee-beng wrote:
>
> On 24/3/2018 6:00 AM, Matthew Knepley wrote:
>
> On Fri, Mar 23, 2018 at 5:23 AM, TAY wee-beng wrote:
>
>>
>> On 21/3/2018 7:47 PM, Matthew Knepley wrote:
>>
>> On Wed, Mar 21, 2018 at 4:59 AM, TAY