Version 1.1.0

• IHasEccentricities: A marker interface used to indicate that an object has Eccentricity Y and Eccentricity Z properties

• StructuralCurveActionAbstractTDirection, TValue: Implemented IHasEccentricities, it already had the eccentricity properties.

• StructuralCurveMember: Implemented IHasEccentricities, it already had the eccentricity properties.

• ModelInformation: Set the default value of the Discipline property to "Structural analysis"

• Instead of returning three Hashset<Guid> containing the IDs of the objects that have are new, changed or deleted, it now returns three IDictionary<Guid, AnalysisModelComparisonEntry>. The keys are the object IDs whilst the values contain additional metadata about the object

• The new AnalysisModelComparisonEntry object holds more metadata about the object that was detected. Instead of just the ID, we now also track the name and type of the object

• The Compare(AnalysisModel, AnalysisModel) has been updated with an overload that accepts a list of types to be skipped during comparison. This is useful when comparing 2 models that originated from different modules and in which the same amount of data cannot be guaranteed. (e.g. ProjectInformation and ModelInformation when importing from BIM+ compared with data imported from Excel)

The LCS transformation service has received a few updates too, functionality that was overlooked during initial development:

• Added transformation for eccentricity Y and Z values on StructuralCurveMember

• Added transformation for eccentricity Y and Z values on StructuralCurveActionTCurveStructuralReference and StructuralCurveMomentTCurveStructuralReference

An issue was discovered when running the validator in the context of .NET Core. The reference validation was not working properly, but first explicitly sorting the objects before starting validation fixed the issue. Initially, the order was implied to be correct due to the way items are added to the model

So now, when calling the Validate(AnalysisModel) method, the objects will be sorted again, based on their dependencies (objects with the least amount of dependencies are validated first)