Refactor System, FFTEngine and FieldCollection
Closed, ResolvedPublic
Actions

Description

Currently, fft_base infers the field to transform form spatial dimension (second order Tensor). However, the fft_engine shouldn't have to know that, and the drawback is that it won't be able to handle symmetric storage of strains
for the solvers, we need to be able to create dynamically sized fields (i.e. nb_components is dynamic). This means that the TypedField class needs to become non-purely virtual
the FieldCollection knows about material dimensions, but shouldn't, it doesn't use it anywhere
The system is badly named, it's going to be called *cell*

Commits: Restricted Differential Revision / rMUSPECTRE9bc97b7e7fa8: Refactoring field collections, FFT engines and solvers

		Status	Assigned	Task
		Resolved	junge	T1851 Refactor System, FFTEngine and FieldCollection
		Resolved	pastewka	T1892 Compare FFT performance between FFTW, ACCFFT, and p3dFFT

junge created this object in space S1 c4science.

junge claimed this task.

junge triaged this task as High priority.

junge renamed this task from Make fft-engines independent from tensorfield to Refactor System, FFTEngine and FieldCollection.Mar 7 2018, 20:41

junge updated the task description. (Show Details)

junge changed the visibility from "Task Author" to "Public (No Login Required)".

junge changed the edit policy from "Task Author" to "µSpectre (Project)".

junge added a revision: Restricted Differential Revision.May 15 2018, 22:35