You need to call close() in these instances: 1. You are completely finished modifying a vector and it's going to go back to the solver (like at the end of an assembly)
2. You are going to switch between "adding" to entries and "setting" entries. You cannot add into a position in the vector and immediately also set into a position in the vector (or vice versa) without calling close() in-between. Actions you do to a vector (like adding or setting) are "queued" up locally and are only actually completed and communicated when you call close(). Derek Sent from my iPad On Feb 8, 2013, at 10:40 AM, Jens Lohne Eftang <[email protected]> wrote: > Hi, > > When do I need to call close() on a NumericVector, and when do I need to > update() a system? > > So far my actions have been based solely on compiler complaints without > any deep understanding of what's going on ... I've been calling close() > on a vector whenever I'm done setting individual elements in a > NumericVector, and I've been calling update() on a system if I've been > modifying the solution vector of a system. > > For example, do I also need to update() a system after changing other > (added) vectors to a system? > > Thanks, > > Jens > > > > ------------------------------------------------------------------------------ > Free Next-Gen Firewall Hardware Offer > Buy your Sophos next-gen firewall before the end March 2013 > and get the hardware for free! Learn more. > http://p.sf.net/sfu/sophos-d2d-feb > _______________________________________________ > Libmesh-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/libmesh-users ------------------------------------------------------------------------------ Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
