Problem
- class compas_fea2.problem.Problem[source]
- Bases: - FEAData- A Problem is a collection of analysis steps (:class:`compas_fea2.problem._Step) applied in a specific sequence. - Parameters:
- namestr, optional
- Uniqe identifier. If not provided it is automatically generated. Set a name if you want a more human-readable input file. 
- describptionstr, optional
- Brief description of the Problem, , by default - None. This will be added to the input file and can be useful for future reference.
 
- Attributes:
- namestr
- Uniqe identifier. If not provided it is automatically generated. Set a name if you want a more human-readable input file. 
- modelcompas_fea2.model.Model
- Model object to analyse. 
- describptionstr
- Brief description of the Problem. This will be added to the input file and can be useful for future reference. 
- stepslist of compas_fea2.problem._Step
- list of analysis steps in the order they are applied. 
- pathstr, pathlib.Path
- Path to the analysis folder where all the files will be saved. 
- path_dbstr, pathlib.Path
- Path to the SQLite database where the results are stored. 
- resultscompas_fea2.results.Results
- Results object with the analyisis results. 
 
 - Warning - Factore Steps are new objects! check the :class:`compas_fea2.problem._Step documentation. - Notes - Problems are registered to a - compas_fea2.model.Model.- Problems can also be used as canonical load combinations, where each load is actually a factored step. For example, a typical load combination such as 1.35*DL+1.50LL can be applied to the model by creating the Steps DL and LL, factoring them (see :class:`compas_fea2.problem.Step documentation) and adding them to Problme - While for linear models the sequence of the steps is irrelevant, it is not the case for non-linear models. - Methods - Inherited Methods - Converts the instance to a string. - Make an independent copy of the data object. - Construct an object of this type from a JSON file. - Construct an object of this type from a JSON string. - Compute a hash of the data for comparison during version control using the sha256 algorithm. - Convert an object to its native data representation and save it to a JSON file. - Convert an object to its native data representation and save it to a JSON string. - Validate the data against the object's data schema.