fluid_flow.i example problem

18 views
Skip to first unread message

Gavin Ridley

unread,
Jun 2, 2017, 5:01:00 PM6/2/17
to moltres-users
Hi all,

I have been trying to run the moltres/problems/fluid_flow.i. I get the error:

*** ERROR ***
A 'INSMomentumNoBCBC' is not a registered object.
We loaded objects from the following libraries and still couldn't find your object:
(NONE)


So, here is my problem. I have:

[gavin][~/projects/moltres]> printenv | grep MOOSE_LIBR
MOOSE_LIBRARY_PATH=/home/gavin/projects/moose/modules/navier_stokes/lib

Is there some kind of MultiApp option missing from the input file?


Alex Lindsay

unread,
Jun 2, 2017, 6:14:36 PM6/2/17
to moltre...@googlegroups.com
Ah, it makes me so happy to have user(s) :-) So the issue is that we're not building Moltres currently with the Navier Stokes module. I did this because while assuming a constant velocity for temperature and precursor advection, we didn't actually need it and it reduced compile time. But if we have somebody interested, then I'll load it in!

You can pull from arfc/moltres `devel` and then run `make` again, and then hopefully you don't see that error again.
--
You received this message because you are subscribed to the Google Groups "moltres-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to moltres-user...@googlegroups.com.
To post to this group, send email to moltre...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/moltres-users/1fa2ccdb-5ab3-4a56-9153-416b7fa7a515%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Alex Lindsay

unread,
Jun 2, 2017, 6:22:12 PM6/2/17
to moltre...@googlegroups.com
Ah, there's another issue here that I'll fix shortly...stay tuned

Alex Lindsay

unread,
Jun 2, 2017, 9:48:31 PM6/2/17
to moltre...@googlegroups.com
Ok Gavin, that input file should run successfully now. It does on my machine. There have been some API changes to the navier stokes module that had to be addressed in a number of input files. There's a good chance that there are other changes lurking around there that haven't been caught. Only our tested input files are protected against MOOSE API changes. Almost certainly more uniform test coverage of kernels and boundary conditions that are used in input files throughout the Moltres repo should be put in place. (Or input files that haven't been used in a long time should be deleted...either way percent coverage should be higher)

Alex
Reply all
Reply to author
Forward
0 new messages