Abstract

The field modelling language FieldML is being developed as a standard for modelling and interchanging field descriptions in software, suitable for a wide range of computation techniques. It comprises a rich set of operators for defining generalized fields as functions of other fields, starting with basic domain fields including sets of discrete objects and coordinate systems. It is extensible by adding new operators and by their arbitrary combination in expressions, making it well suited for describing the inherent complexity of biological materials and organ systems. This paper describes the concepts behind FieldML, including a simple example of a spatially varying finite-element field. It outlines current implementations in established, open source computation and visualization software, both drawing on decades of bioengineering modelling software development experience.

Highlights

  • A field is an abstraction of some quantity defined over a domain

  • It is noted that the more varied field representations in CMISS come at the cost of greater software complexity, which FieldML intends to reduce by replacing fixed-functionality codes with modular combinations of basic field operations

  • FieldML defines modular field operators acting on argument fields of particular value types, but which usually do not know the ultimate domain over which those fields are defined

Read more

Summary

Introduction

A field is an abstraction of some quantity defined over a domain. To mathematically model the physics of real-world bodies, fields describing physical state and other properties at locations within the domain are approximated by functions based on a finite set of parameter values. FieldML avoids complex data structures for defining fields such as meshes with fixed notions of connectivity, and instead defines fields in terms of more abstract domains including sets and coordinate systems These domains are each a type of field whose values are object references or coordinate system locations. FieldML is expressive since the value of each field at domain locations is explicitly stated by functions It is extensible via the definition of new field operators or types, and their combination in expressions. Concepts are illustrated with a mock-up serialization of a spatially varying finite-element field, but the issue of developing FieldML serialization formats is mostly left to later work and is reliant on consensus on the data model, and the availability of software interfaces and implementations. The authors invite feedback and other contributions towards the development of the FieldML standard

Background
Example: finite-element interpolation
FieldML implementations
Discussion
Full Text
Paper version not known

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call

Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.