Skip to content

Upgrade to Gridap 1.6 issues #31

@amartinhuertas

Description

@amartinhuertas

Hi @fverdugo, @santiagobadia,

FYI ... in PR #32, I ported GridapDistributed.jl to Gridap 0.16.3. Along the process, I annotated a set of concerns that you can find in the list below. Apart from solving this, I think it would be great to speak about which are the priorities/future plans with the development of GridapDistributed.jl.

Several concerns I have detected along the process.

  • SparseMatrixAssembler in Gridap v0.16 does no longer conceptually hold test and trial FE spaces inside, while DistributedSparseMatrixAssembler does.
  • Introduction of ArtificeSparseMatrixToLeverageDefaults. Something more clever to solve this issue?
  • Review the need for the allocate_local_vector function and the workflow associated to it. Is there a better way to design this taking into account the way assembly operations have been redesigned in Gridap v0.16?
  • I am skipping symbolic_loop_vector! all the way through.
  • [Solved in cc56f4d] Bilinear and linear functions for multifield problems cannot be iterated over (i.e., tuples) as in Gridap.
  • I had to recover Reindexed and some of the associated machinery from Gridap 0.14.3. I need it for GridapDistributed.jl. Should we bypass this need? If yes, how?
  • Review DistributedFEFunctions and their current hierarchy.
  • Gridap.Algebra.add_entry!: We are inserting entries one by one. To see how we can introduce all cell entries at once with the new assembly interface.

Metadata

Metadata

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions