> > There's two different add_vector functions here. The one being called > like force.add_vector() just means that the element's DenseVector > called Fe is being summed into the global NumericVector called force. > You don't want that. > > The System::add_vector() function stores another NumericVector in > System. You might or might not want this. It's less flexible but it > might be easier to use. Here's the limitation: when you do a > System::add_vector(), the new vector has the exact same structure as > your solution vector. So if your solution has one component T and you > need to store gradT_x, gradT_y, and gradT_z, you'd need to add three > vectors for that. If your solution has a second component you and you > don't need to store gradu_x, gradu_y, and gradu_z, too bad, because > the vectors created by add_vector will all have space for u variables > anyway. > --- > Roy > Thanks! I thought the System::add_vector() stores the arbitrary vectors. I appreciate your explanation. So the System::add_variable() will be a good choice to define the flux component such as gradT_x, gradT_y, If I just want to dump the these flux solution, right?
Liang ------------------------------------------------------------------------------ _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
