{"action":"created","issue":{"url":"https://api.github.com/repos/tbeu/fmi-standard/issues/370","repository_url":"https://api.github.com/repos/tbeu/fmi-standard","labels_url":"https://api.github.com/repos/tbeu/fmi-standard/issues/370/labels{/name}","comments_url":"https://api.github.com/repos/tbeu/fmi-standard/issues/370/comments","events_url":"https://api.github.com/repos/tbeu/fmi-standard/issues/370/events","html_url":"https://github.com/tbeu/fmi-standard/issues/370","id":370365852,"node_id":"MDU6SXNzdWUzNzAzNjU4NTI=","number":370,"title":"Clarifications needed in FMI 1.0 to be added to FMI 1.0.1","user":{"login":"modelica-trac-importer","id":22202507,"node_id":"MDQ6VXNlcjIyMjAyNTA3","avatar_url":"https://avatars1.githubusercontent.com/u/22202507?v=4","gravatar_id":"","url":"https://api.github.com/users/modelica-trac-importer","html_url":"https://github.com/modelica-trac-importer","followers_url":"https://api.github.com/users/modelica-trac-importer/followers","following_url":"https://api.github.com/users/modelica-trac-importer/following{/other_user}","gists_url":"https://api.github.com/users/modelica-trac-importer/gists{/gist_id}","starred_url":"https://api.github.com/users/modelica-trac-importer/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/modelica-trac-importer/subscriptions","organizations_url":"https://api.github.com/users/modelica-trac-importer/orgs","repos_url":"https://api.github.com/users/modelica-trac-importer/repos","events_url":"https://api.github.com/users/modelica-trac-importer/events{/privacy}","received_events_url":"https://api.github.com/users/modelica-trac-importer/received_events","type":"User","site_admin":false},"labels":[{"id":1091877065,"node_id":"MDU6TGFiZWwxMDkxODc3MDY1","url":"https://api.github.com/repos/tbeu/fmi-standard/labels/P:%20major","name":"P: major","color":"f6f6f6","default":false},{"id":1091874831,"node_id":"MDU6TGFiZWwxMDkxODc0ODMx","url":"https://api.github.com/repos/tbeu/fmi-standard/labels/specification","name":"specification","color":"0000aa","default":false},{"id":1091877746,"node_id":"MDU6TGFiZWwxMDkxODc3NzQ2","url":"https://api.github.com/repos/tbeu/fmi-standard/labels/task","name":"task","color":"cccccc","default":false}],"state":"open","locked":false,"assignee":{"login":"tbeu","id":5444067,"node_id":"MDQ6VXNlcjU0NDQwNjc=","avatar_url":"https://avatars0.githubusercontent.com/u/5444067?v=4","gravatar_id":"","url":"https://api.github.com/users/tbeu","html_url":"https://github.com/tbeu","followers_url":"https://api.github.com/users/tbeu/followers","following_url":"https://api.github.com/users/tbeu/following{/other_user}","gists_url":"https://api.github.com/users/tbeu/gists{/gist_id}","starred_url":"https://api.github.com/users/tbeu/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/tbeu/subscriptions","organizations_url":"https://api.github.com/users/tbeu/orgs","repos_url":"https://api.github.com/users/tbeu/repos","events_url":"https://api.github.com/users/tbeu/events{/privacy}","received_events_url":"https://api.github.com/users/tbeu/received_events","type":"User","site_admin":false},"assignees":[{"login":"tbeu","id":5444067,"node_id":"MDQ6VXNlcjU0NDQwNjc=","avatar_url":"https://avatars0.githubusercontent.com/u/5444067?v=4","gravatar_id":"","url":"https://api.github.com/users/tbeu","html_url":"https://github.com/tbeu","followers_url":"https://api.github.com/users/tbeu/followers","following_url":"https://api.github.com/users/tbeu/following{/other_user}","gists_url":"https://api.github.com/users/tbeu/gists{/gist_id}","starred_url":"https://api.github.com/users/tbeu/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/tbeu/subscriptions","organizations_url":"https://api.github.com/users/tbeu/orgs","repos_url":"https://api.github.com/users/tbeu/repos","events_url":"https://api.github.com/users/tbeu/events{/privacy}","received_events_url":"https://api.github.com/users/tbeu/received_events","type":"User","site_admin":false}],"milestone":{"url":"https://api.github.com/repos/tbeu/fmi-standard/milestones/8","html_url":"https://github.com/tbeu/fmi-standard/milestone/8","labels_url":"https://api.github.com/repos/tbeu/fmi-standard/milestones/8/labels","id":3740120,"node_id":"MDk6TWlsZXN0b25lMzc0MDEyMA==","number":8,"title":"FMI 1.0.1","description":"","creator":{"login":"modelica-trac-importer","id":22202507,"node_id":"MDQ6VXNlcjIyMjAyNTA3","avatar_url":"https://avatars1.githubusercontent.com/u/22202507?v=4","gravatar_id":"","url":"https://api.github.com/users/modelica-trac-importer","html_url":"https://github.com/modelica-trac-importer","followers_url":"https://api.github.com/users/modelica-trac-importer/followers","following_url":"https://api.github.com/users/modelica-trac-importer/following{/other_user}","gists_url":"https://api.github.com/users/modelica-trac-importer/gists{/gist_id}","starred_url":"https://api.github.com/users/modelica-trac-importer/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/modelica-trac-importer/subscriptions","organizations_url":"https://api.github.com/users/modelica-trac-importer/orgs","repos_url":"https://api.github.com/users/modelica-trac-importer/repos","events_url":"https://api.github.com/users/modelica-trac-importer/events{/privacy}","received_events_url":"https://api.github.com/users/modelica-trac-importer/received_events","type":"User","site_admin":false},"open_issues":1,"closed_issues":2,"state":"closed","created_at":"2018-10-15T15:13:20Z","updated_at":"2018-10-15T22:18:14Z","due_on":null,"closed_at":"2018-10-15T15:13:20Z"},"comments":10,"created_at":"2018-10-15T22:18:14Z","updated_at":"2018-10-15T22:20:49Z","closed_at":null,"author_association":"COLLABORATOR","body":"**Modified by andreas&#46;junghanns on 5 May 2016 12:14 UTC**\nThis ticket is a collection of clarification needed in case we decide to have a maintenance-release of FMI 1.0.\n\n|= variant effected =|= description =|= severity, 1-low, 3-high =|= suggested fix =|= compatibility issues for the suggested fix =|\n|-|-|-|-|-|\n|CS |  unclear meaning of the fmuLocation argument of the fmiInstantiateSlave function. Is it: the path to a directory that contains the extracted (unzipped) content of the FMU, with exactly the same directory hierarchy as in the zip file? or just the path to the FMU file itself? | 2 | The text now seems to mean the location of the FMU. Clarify. | potentially severe|\n|ME, CS | is it allowed to call the get/set functions with zero-length array arguments? At least two possibilities: it is allowed, and the function returns fmiOK; it is not allowed, and the function returns fmiDiscard. | 1 | I think we should be liberal and allow zero-length | none|\n|CS | remove the canSignalEvents from the list of co-simulation capability flags since there is no way for the FMU to do this. | 1 | agreed, maybe we should also cleanup the appendix | none|\n|ME | fix the issue #74 about displayUnit. | 2 | The ticket #74 suggests the obvious fixes | none (most people must have implemented that correctly)|\n|ME, CS | In the current 1.0 specification, nothing is stated about that and some FMU define aliased variables that have different start values. This yields nondeterministic behaviour at initialization. Only one start value should be allowed for each group of aliased variables. | 3 | forbid aliased start value. | none - improving this only removes ambiguity|\n|ME, CS | allow additional DLLs or shared libraries in the binaries/<platform> subdirectory that can be loaded by the FMU main DLL or shared library. | 2 | small sentence should do the trick | none - this is what most implementations already do, we just sanction standard practise|\n|ME | the definition ti = limeps?0 ti+eps from page 11 of document (mathematical description of Model Exchange, section 2.1) is meaningless. | 1 | remove it | none|\n|ME | fmiGetStateValueReferences must return either fmiUndefinedValueReference or a value reference of a variable which is declared in the XML model description. | 1 | add this in the function description | none|\n|ME | it is unclear if the importer has to call fmiEventUpdate after a discrete variable changed, or if this should be auto detected | 3 | we should clarify that the importer has to call fmiEventUpdate explicitly | small, if some FMUs handle this themselves now, calling the fmiEventUpdate a second time should not hurt|\n|ME, CS | we need to clarify the license conditions | 1 | simply add a reference to the CCLA in the document | none|\n|CS | Appendix B speculates about future versions. | 1 | remove Appendix B | none|\n\n\n\n----\n\n**Modified by andreas&#46;junghanns on 5 May 2016 12:12 UTC**\nThis ticket is a collection of clarification needed in case we decide to have a maintenance-release of FMI 1.0.\n\n|= variant effected =|= description =|= severity, 1-low, 3-high =|= suggested fix =|= compatibility issues for the suggested fix =|\n|-|-|-|-|-|\n|CS |  unclear meaning of the fmuLocation argument of the fmiInstantiateSlave function. Is it: the path to a directory that contains the extracted (unzipped) content of the FMU, with exactly the same directory hierarchy as in the zip file? or just the path to the FMU file itself? | 2 | The text now seems to mean the location of the FMU. Clarify. | potentially severe|\n|ME, CS | is it allowed to call the get/set functions with zero-length array arguments? At least two possibilities: it is allowed, and the function returns fmiOK; it is not allowed, and the function returns fmiDiscard. | 1 | I think we should be liberal and allow zero-length | none|\n|CS | remove the canSignalEvents from the list of co-simulation capability flags since there is no way for the FMU to do this. | 1 | agreed, maybe we should also cleanup the appendix | none|\n|ME, CS | fix the issue #74 about displayUnit. | 2 | The ticket #74 suggests the obvious fixes | none (most people must have implemented that correctly)|\n|ME, CS | In the current 1.0 specification, nothing is stated about that and some FMU define aliased variables that have different start values. This yields nondeterministic behaviour at initialization. Only one start value should be allowed for each group of aliased variables. | 3 | forbid aliased start value. | none - improving this only removes ambiguity|\n|ME, CS | allow additional DLLs or shared libraries in the binaries/<platform> subdirectory that can be loaded by the FMU main DLL or shared library. | 2 | small sentence should do the trick | none - this is what most implementations already do, we just sanction standard practise|\n|ME | the definition ti = limeps?0 ti+eps from page 11 of document (mathematical description of Model Exchange, section 2.1) is meaningless. | 1 | remove it | none|\n|ME | fmiGetStateValueReferences must return either fmiUndefinedValueReference or a value reference of a variable which is declared in the XML model description. | 1 | add this in the function description | none|\n|ME | it is unclear if the importer has to call fmiEventUpdate after a discrete variable changed, or if this should be auto detected | 3 | we should clarify that the importer has to call fmiEventUpdate explicitly | small, if some FMUs handle this themselves now, calling the fmiEventUpdate a second time should not hurt|\n|ME, CS | we need to clarify the license conditions | 1 | simply add a reference to the CCLA in the document | none|\n|CS | Appendix B speculates about future versions. | 1 | remove Appendix B | none|\n\n\n\n----\n\n**Modified by andreas&#46;junghanns on 5 May 2016 10:48 UTC**\nThis ticket is a collection of clarification needed in case we decide to have a maintenance-release of FMI 1.0.\n\n|= variant effected =|= description =|= severity, 1-low, 3-high =|= suggested fix =|= compatibility issues for the suggested fix =|\n|-|-|-|-|-|\n|CS |  unclear meaning of the fmuLocation argument of the fmiInstantiateSlave function. Is it: the path to a directory that contains the extracted (unzipped) content of the FMU, with exactly the same directory hierarchy as in the zip file? or just the path to the FMU file itself? | 2 | The text now seems to mean the location of the FMU. Clarify. | potentially severe|\n|ME, CS | is it allowed to call the get/set functions with zero-length array arguments? At least two possibilities: it is allowed, and the function returns fmiOK; it is not allowed, and the function returns fmiDiscard. | 1 | I think we should be liberal and allow zero-length | none|\n|CS | remove the canSignalEvents from the list of co-simulation capability flags since there is no way for the FMU to do this. | 1 | agreed, maybe we should also cleanup the appendix | none|\n|ME, CS | fix the issue #74 about displayUnit. | 2 | The ticket #74 suggests the obvious fixes | none (most people must have implemented that correctly)|\n|ME, CS | In the current 1.0 specification, nothing is stated about that and some FMU define aliased variables that have different start values. This yields nondeterministic behaviour at initialization. Only one start value should be allowed for each group of aliased variables. | 3 | forbid aliased start value. | none - improving this only removes ambiguity|\n|ME, CS | allow additional DLLs or shared libraries in the binaries/<platform> subdirectory that can be loaded by the FMU main DLL or shared library. | 2 | small sentence should do the trick | none - this is what most implementations already do, we just sanction standard practise|\n|ME | the definition ti = limeps?0 ti+eps from page 11 of document (mathematical description of Model Exchange, section 2.1) is meaningless. | 1 | remove it | none|\n|ME | fmiGetStateValueReferences must return either fmiUndefinedValueReference or a value reference of a variable which is declared in the XML model description. | 1 | add this in the function description | none|\n|ME | it is unclear if the importer has to call fmiEventUpdate after a discrete variable changed, or if this should be auto detected | 3 | we should clarify that the importer has to call fmiEventUpdate explicitly | small, if some FMUs handle this themselves now, calling the fmiEventUpdate a second time should not hurt|\n|ME, CS | we need to clarify the license conditions | 1 | simply add a reference to the CCLA in the document | none|\n\n\n\n----\n\n**Modified by andreas&#46;junghanns on 5 May 2016 10:47 UTC**\nThis ticket is a collection of clarification needed in case we decide to have a maintenance-release of FMI 1.0.\n\n|= variant effected =|= description =|= severity, 1-low, 3-high =|= suggested fix =|= compatibility issues for the suggested fix =|\n|-|-|-|-|-|\n|CS |  unclear meaning of the fmuLocation argument of the fmiInstantiateSlave function. Is it:|\n\n        the path to a directory that contains the extracted (unzipped) content of the FMU, with exactly the same directory hierarchy as in the zip file?\n        or just the path to the FMU file itself? || 2 || The text now seems to mean the location of the FMU. Clarify. || potentially severe ||\n\n|ME, CS | is it allowed to call the get/set functions with zero-length array arguments? At least two possibilities: it is allowed, and the function returns fmiOK; it is not allowed, and the function returns fmiDiscard. | 1 | I think we should be liberal and allow zero-length | none|\n|-|-|-|-|-|\n|CS | remove the canSignalEvents from the list of co-simulation capability flags since there is no way for the FMU to do this. | 1 | agreed, maybe we should also cleanup the appendix | none|\n|ME, CS | fix the issue #74 about displayUnit. | 2 | The ticket #74 suggests the obvious fixes | none (most people must have implemented that correctly)|\n|ME, CS | In the current 1.0 specification, nothing is stated about that and some FMU define aliased variables that have different start values. This yields nondeterministic behaviour at initialization. Only one start value should be allowed for each group of aliased variables. | 3 | forbid aliased start value. | none - improving this only removes ambiguity|\n|ME, CS | allow additional DLLs or shared libraries in the binaries/<platform> subdirectory that can be loaded by the FMU main DLL or shared library. | 2 | small sentence should do the trick | none - this is what most implementations already do, we just sanction standard practise|\n|ME | the definition ti = limeps?0 ti+eps from page 11 of document (mathematical description of Model Exchange, section 2.1) is meaningless. | 1 | remove it | none|\n|ME | fmiGetStateValueReferences must return either fmiUndefinedValueReference or a value reference of a variable which is declared in the XML model description. | 1 | add this in the function description | none|\n|ME | it is unclear if the importer has to call fmiEventUpdate after a discrete variable changed, or if this should be auto detected | 3 | we should clarify that the importer has to call fmiEventUpdate explicitly | small, if some FMUs handle this themselves now, calling the fmiEventUpdate a second time should not hurt|\n|ME, CS | we need to clarify the license conditions | 1 | simply add a reference to the CCLA in the document | none|\n\n\n\n----\n\n**Reported by andreas&#x2e;junghanns on 3 Mar 2016 16:34 UTC**\nThis ticket is a collection of clarification needed in case we decide to have a maintenance-release of FMI 1.0.\n\nPlease add here in the ticket description your points:\n - add reference to CCLA\n - call/don't call eventUpdate() on discrete variable change\n\n----\n\nMigrated-From: https://trac.fmi-standard.org/ticket/370"},"comment":{"url":"https://api.github.com/repos/tbeu/fmi-standard/issues/comments/430034479","html_url":"https://github.com/tbeu/fmi-standard/issues/370#issuecomment-430034479","issue_url":"https://api.github.com/repos/tbeu/fmi-standard/issues/370","id":430034479,"node_id":"MDEyOklzc3VlQ29tbWVudDQzMDAzNDQ3OQ==","user":{"login":"modelica-trac-importer","id":22202507,"node_id":"MDQ6VXNlcjIyMjAyNTA3","avatar_url":"https://avatars1.githubusercontent.com/u/22202507?v=4","gravatar_id":"","url":"https://api.github.com/users/modelica-trac-importer","html_url":"https://github.com/modelica-trac-importer","followers_url":"https://api.github.com/users/modelica-trac-importer/followers","following_url":"https://api.github.com/users/modelica-trac-importer/following{/other_user}","gists_url":"https://api.github.com/users/modelica-trac-importer/gists{/gist_id}","starred_url":"https://api.github.com/users/modelica-trac-importer/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/modelica-trac-importer/subscriptions","organizations_url":"https://api.github.com/users/modelica-trac-importer/orgs","repos_url":"https://api.github.com/users/modelica-trac-importer/repos","events_url":"https://api.github.com/users/modelica-trac-importer/events{/privacy}","received_events_url":"https://api.github.com/users/modelica-trac-importer/received_events","type":"User","site_admin":false},"created_at":"2018-10-15T22:20:49Z","updated_at":"2018-10-15T22:20:49Z","author_association":"COLLABORATOR","body":"**Modified by andreas&#46;junghanns on 6 May 2016 08:58 UTC**"}}
{"actor":{"display_login":"modelica-trac-importer"}}