{"push_id":2578064889,"size":1,"distinct_size":1,"ref":"refs/heads/dgref","head":"915fac2aee6e83685043d6075a7db8411f5227ba","before":"db2e1f3f9a403b4f52d720c6da72663b20de7702","commits":[{"sha":"915fac2aee6e83685043d6075a7db8411f5227ba","author":{"name":"Jozsef Bakosi","email":"4c6fa3afd61a0a24ca3d63b27d7427400d29412f@lanl.gov"},"message":"Revamp boundary conditions data for nodal discretizations\n\nThe main reason for this change is to adopt the strategy to transfer and\npartition the data required to set boundary conditions from file to\nworker chares as was done for DG. Though DG needs boundary faces and\ntheir connectivities (given by triangle global node IDs), CG (both MatCG\nand DiagCG) needs node lists associated to side sets. This data is first\nread from file then it is distributed to each worker chare for use\nduring time stepping (after global mesh node reordering).\n\nPreviously, the node lists associated to side sets were read from file\nusing an ExodusII API call that reads the node lists directly. However,\nsince DG needs faces and face-triangle connectivity (which is more\ninformation than simple lists of nodes), there is no reason to not\npiggyback on the machinery already done for DG and derive the node lists\nfrom it. This step is done in Partitioner::createWorkers(), modifying\nthe main loop there.\n\nThis change consolidates and significantly simplifies code and logic,\nand enables better code reuse. Additionally, this change will also\nenable a common treatment of updating these data structures during\ninitial mesh refinement. This latter is not yet done, that is next,\nbased on this preliminary step, points 5 and 6 of #236.","distinct":true,"url":"https://api.github.com/repos/quinoacomputing/quinoa/commits/915fac2aee6e83685043d6075a7db8411f5227ba"}]}
{"actor":{"display_login":"jbakosi"}}