Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add cylinder flag fsi test #571

Open
wants to merge 4 commits into
base: master
Choose a base branch
from

Conversation

richardschu
Copy link
Contributor

. add a 2D test for the FSI application cylinder_with_flag
. introduce a scaling factor for the end_time used in the application to shorten the test duration
. compute reference values of velocity, pressure and displacement to compare in the generated output ("absolute error" taking zero as "exact solution")
. suppress iteration count and wall time output by mesh motion ale_mapping->update called during ALE update in fluid solver

@richardschu
Copy link
Contributor Author

... this is to remind me that I should check if the test was actually picked up

@@ -148,10 +148,9 @@ SolverFluid<dim, Number>::setup(std::shared_ptr<FluidFSI::ApplicationBase<dim, N
// initialize time_integrator
helpers_ale = std::make_shared<HelpersALE<Number>>();

bool print_solver_info = is_test ? false : time_integrator->print_solver_info();
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am not sure if this works as intended because time_integrator->print_solver_info() might be true/false depending on the time step (say solver info is going to be printed every 10th time step). However, the variable print_solver_info will then take the same value throughout a whole simulation, doesn't it?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I moved it inside now, this is work in progress :)

@richardschu
Copy link
Contributor Author

halleluja
@nfehn
ready for review anytime :)

Copy link
Contributor

@kronbichler kronbichler left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A few random comments.

@@ -30,3 +30,5 @@ TARGETNAME(TARGET_NAME ${CMAKE_CURRENT_SOURCE_DIR})
PROJECT(${TARGET_NAME})

EXADG_PICKUP_EXE(solver.cpp ${TARGET_NAME} solver)

ADD_SUBDIRECTORY(tests)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you please insert a line break at the end of the file.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

sure, is something like this the reason?

@@ -178,19 +200,20 @@ class Application : public FluidFSI::ApplicationBase<dim, Number>

// PHYSICAL QUANTITIES
param.start_time = 0.0;
param.end_time = END_TIME;
param.end_time = END_TIME * end_time_factor;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we really introduce a factor for the time via the input file, but keep the END_TIME as a separate variable? I would prefer to specify the actual final time, because setting information in two places is usually confusing.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

hmmm ... I did not want to throw away the heuristic
double const END_TIME = 4.0 * L / U_MEAN;
that is the only reason I kept this. If I were to write this application from scratch, I would give the end_time to the user to provide in the .json file.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants