Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
Invoke interface without preference switches for Latency Analysis got lost #1710
It does not use the preference settings. It uses the default settings that are documented as part of the analysis. I could leave the method out and instead have an entry in the method registry with those parameters supplied. Or we could argue that they should not even be set there and users have to list them on every verification activity call. Furthermore, one of the parameters is SOM. The method passes in ‘null’. If I have to do this in the registry or verification activity I do not have a way of expressing ‘null’. From: Lutz Wrage [mailto:firstname.lastname@example.org] Sent: Sunday, February 24, 2019 10:32 AM To: osate/osate2 <email@example.com> Cc: Peter Feiler <firstname.lastname@example.org>; Assign <email@example.com> Subject: Re: [osate/osate2] Invoke interface without preference switches for Latency Analysis got lost (#1710) I assume this method uses the OSATE preference settings: Should such a method even exist? It may be better not to provide it at all because the result depends on something that is neither part of the model nor part of any ALISA specification. — You are receiving this because you were assigned. Reply to this email directly, view it on GitHub<#1710 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AAtzuAbcRUQ_ItiNHrcVMPpSsLnU_YB_ks5vQrBggaJpZM4bKyUX>.