Brian,
Thanks for the info! I changed the precision to 'single' in the .ini file,
and the Couette flow took slightly longer than the double precision case
(5:39 vs 5:43)! I don't really know what's going on right now so I'm going
to start by testing my CUDA installation, pycuda, and pyfr, respectively to
see what the issue is. Do you have any ideas off the top of your head?
Considering that you could trade 4 Nvidia Tesla P100 cards for a Tesla
Model 3 at current market values, I don't think there will be any just
lying around at school. However, if I can get some of my cases working, the
new graham cluster is equipped with a bunch of heterogeneous computing
nodes with Tesla P100s.
Nolan
On Saturday, July 1, 2017 at 6:51:05 PM UTC-4, nnunn wrote:
>
> Hi Nolan Dyck - thanks for the helpful setup instructions!
> Re: "weird command-line printout...", I run Visual Studio 2015 on Win7,
> and saw that sort of output when stepping under Visual Studio debugger.
> For normal runs, I get a neat console-mode "progress bar" by adding the
> following block near the end of pyfr/progress_bar.py:
>
> # Write the progress bar and pad the remaining columns
> if sys.platform == 'win32':
> # NN: for windows console
> sys.stdout.write('\b' * 80)
> sys.stdout.write('\r')
> sys.stdout.write(s)
> sys.stdout.flush()
> else:
> sys.stderr.write('\x1b[2K\x1b[G')
> sys.stderr.write(s)
> sys.stderr.flush()
>
> # Update the last render time
> self._last_wallt = wallt
>
>
> Nigel
>
>
>
> On Saturday, July 1, 2017 at 6:39:58 AM UTC+10, Nolan Dyck wrote:
>
> Hello PyFR community,
>>
>
>>
--
You received this message because you are subscribed to the Google Groups "PyFR
Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send an email to [email protected].
Visit this group at https://groups.google.com/group/pyfrmailinglist.
For more options, visit https://groups.google.com/d/optout.
