I understood your advise.I seem to have modified thefile again this time 
because I have often modified "RB_construction.C"to printoutput error bounds 
during an offline stage.Thank you for reminding me of a better way.Best 
regards,Kang------------------------------------------------------------
ShinseongKang
GraduateStudent
PusanNationalUniversity, South KoreaTel.: +82-051-510-3052
H.P.:+82-010-9770-6595
E-mail:ss.k...@pusan.ac.kr

----------------------------------------------------------------- Original 
Message -----From : David Knezevic <david.kneze...@akselos.com>To : "Shinseong 
Kang" <ss.k...@pusan.ac.kr>Cc : "Libmesh user group" 
<libmesh-users@lists.sourceforge.net>Sent : 2019-10-10 10:15:15Subject : Re: 
[RE]Re: [RB] Assembly for a Interior (neighbor) side between elementsAs 
youadvised, I edited that part in "RB_construction.C" and ranmy code again.As a 
result, I could obtain the correct result.OK, good to hear! By the way, I 
didn't mean that you need to edit rb_construction.C. Theimpose_internal_fluxes 
boolean is a public member of the RBConstruction class, so you can just set 

impose_internal_fluxes 

to true in the RBConstruction object that you're using. You can do that in your 
application code, no need to edit the libMesh library code.Best,David----- 
Original Message -----From : David Knezevic <david.kneze...@akselos.com>To : 
"Shinseong Kang" <ss.k...@pusan.ac.kr>Cc : "Libmesh user group" 
<libmesh-users@lists.sourceforge.net>Sent : 2019-10-08 21:53:36Subject : Re: 
[RB] Assembly for a Interior (neighbor) side between elementsHello,I think your 
approach is basically correct, butissue is that by default the code skips 
assembly on internal sides for the sake of efficiency (since usually we do not 
need to do assembly on internal sides). In order to not skip internal sides you 
can set "impose_internal_fluxes = true" on your RBConstruction object. That is 
false by default and if you look 
atRBConstruction::add_scaled_matrix_and_vector() you will see that you have to 
set it to true in order to loop over non-boundary sides.Let me know if that 
works for you.Best,DavidOn Tue, Oct 8, 2019 at 6:57 AM Shinseong Kang 
<ss.k...@pusan.ac.kr> wrote:Hello, all.I triedto definean output in a simply 
supported 3-D beam problem.My output is an average displacement in the middle 
of the beam.For simplicity, I only used two brick elements, i.e, ■|■, where"■" 
is an element, and"|" is a location I want to compute the average output.To do 
this, I utilized the codes in RB example 5.First, Ideclared "ThetaOutput" 
(parameter-dependent term) and alsodeclared "AssemblyOutput" 
(parameter-independent term) as 
follows:=======================================voidAssemblyOutput::boundary_assembly(FEMContext
 & c)}=======================================As you can see, The above code is 
very similar to"Assemblyp1" in "assembly.C" ofRB example 5.However, I could not 
obtain the correct output because the above code cannot deal with interior side 
between elements.In other words, theboundary information of FEMContext only 
include outer side.I tried to find another way, but I could not find the right 
solution.Therefore,I'd like your help.To summarize my questions areas 
follows:1. Is there any way to assemble an interior (neighbor) sidebetween 
elements?2. How to compute anaverage displacement for the middleof a beam in 
terms of the RB codes?Thank you.Best 
regards,Kang------------------------------------------------------------
ShinseongKang
GraduateStudent
PusanNationalUniversity, South KoreaTel.: +82-051-510-3052
H.P.:+82-010-9770-6595
E-mail:ss.k...@pusan.ac.kr

------------------------------------------------------------
_______________________________________________
Libmesh-users mailing list
Libmesh-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libmesh-users

Reply via email to