Conversation
… if the first was invalid (i.e. DifferentialTemperature with > 2 positions)
…ferentialTemperatureLoad` (#452)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Lusas_Toolkit
Feature
BarDifferentialTempatureLoadandAreaDifferentialTemperatureLoadBarDifferentialLoad;AreaDifferentialLod;IFProfileTemperartureLoadobject in Lusas. Given that Lusas uses absolute distances and the BHoM objects use parametric distances only profiles that have top/bottom temperatures are supported for now.Offsetfrom Lusas (referred to as eccentricies) note Lusas has different origins for offsets which are accounted for when read whereasOffsetis defined from the Centroid;Offsetfrom Lusas (these eccentricies are always defined from the centroid as per the BHoM convention). Only constant offsets are supported in Lusas;Offsetobjects forTaperedProfileonly constant offsets are supported despite being able to set for each profile the section has to align to one profile.MapDomainwas not being correctly applied,Compliance