Error while running example1 from the folder "problems"

[ananthanarasimhanj]

I installed crane, and all tests passed that i verified that its intalled successfully. After that, I tried to run example1 from the problems folder. and I am getting the following error.

ERROR /home/ananth/projects/crane/problems/example1.i:41: unused parameter 'ChemicalReactions/ScalarNetwork/reaction_coefficient_format'

Stack frames: 10 0: libMesh::print_trace(std::ostream&) 1: moose::internal::mooseErrorRaw(std::cxx11::basic_string<char, std::char_traits, std::allocator >, std::cxx11::basic_string<char, std::char_traits, std::allocator >) 2: void mooseError<std::cxx11::basic_string<char, std::char_traits, std::allocator >&>(std::cxx11::basic_string<char, std::char_traits, std::allocator >&) 3: Parser::errorCheck(libMesh::Parallel::Communicator const&, bool, bool) 4: MooseApp::errorCheck() 5: MooseApp::executeExecutioner() 6: MooseApp::run() 7: main 8: __libc_start_main 9: ../crane-opt(+0x23ef) [0x558530fc83ef] application called MPI_Abort(MPI_COMM_WORLD, 1) - process 0 [unset]: write_line error; fd=-1 buf=:cmd=abort exitcode=1 : system msg for write_line failure : Bad file descriptor

[smpeyres]

Hi Ananth! Sorry for the delayed reply. I just cloned a fresh version of crane, and example1.i ran just fine for me.

I don't think any of the recent commits affected the used/unused parameters, so my best guess is that you didn't install crane correctly or you didn't run the example correctly. Are you still experiencing this issue?

[ananthanarasimhanj]

Hi @smpeyres! No issues. I was working with Zapdos during this time. I am yet to try examples from Crane. whether the syntax is same as the one used for Zapdos to run a ".i" file?

[smpeyres]

Yes, the syntax is very similar!

Assuming you have MOOSE activated, you installed crane correctly (run the tests!), and you are in the problems directory where example1.i is stored, you should run the following in the terminal:

../crane-opt -i example1.i

If you were within a directory within Zapdos, the syntax is similar:

../zapdos-opt -i <file name>

Keep in mind that

../<app name>-opt

points to the Makefile. If you are another directory deep, say in problems/argon_microdischarge, you need to point one directory higher:

../../<app name>-opt

Running

../zapdos-opt -i example1.i

will not work if you are in directory within crane!

I hope this helped; let me know if you have any more questions or concerns!