GlossaryΒΆ
This section aims to describe the vocabulary used to describe Nasca’s components.
A run of Nasca performs one study. Each study focuses on one model (FEM) and one set of results (wether multi-loadcases or not). To achieve this, a study is composed of several analysis which will focus on one set of items.
- Study
- A study is the full analysis of a FEM and leads to report and/or spreadsheets describincg of steg results. A study is a set of analysis.
- Analysis
- An analysis is the base component of a study. An analysis is based on a set of items (e.g. panels, joints, fasteners, etc.) and consists in a stack of steps to be performed to get the results.
- Item
An item is a set of elements and nodes (elements and nodes to be understood in the context of a Finite Elements Model) grouped together to form a high-level element (e.g. panel2, joint7, etc.).
Items are the real added-value of Nasca by providing a concrete abstraction layer over finite elements.
All the items of same nature are grouped together into a proper container called Collector.
Each item from a single collector are identified via a unique Nasca ID (frequently abbreviated as nid).
- nid
- refers to Nasca ID. This integer identifies an item inside its collector. For example Panel7, Joint7, etc..
- Collector
- A Collector is the container of items of the same familly. By extension, it also refers to the plugin performing the grouping.
- Plugin
- Piece of code extending Nasca’s base possibilities. Three kinds of plugins exist: Collectors, Analysts and Writers. Check the plugins overview.
- Pipeline
pipeline concept is the easiest way to figure dataflow managemnt. A pipeline is a list of steps to be performed to get the analysis results.
A pipeline can actually be straight or forked.
