Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FMU Proxy URI is not recognised as a simulator source #74

Open
THEvang opened this issue Jun 22, 2020 · 4 comments
Open

FMU Proxy URI is not recognised as a simulator source #74

THEvang opened this issue Jun 22, 2020 · 4 comments
Assignees
Labels
bug Something isn't working

Comments

@THEvang
Copy link
Member

THEvang commented Jun 22, 2020

OSP Validator does not recognise FMUs with fmu proxy is source. For instance, <Simulator name="vessel_model" source="fmu-proxy://localhost:9090?guid=b71f76f7-b51e-40d5-affb-f63905622e2b" stepSize="0.05"/> gives the following error message:

Exception in thread "main" java.lang.RuntimeException: java.lang.RuntimeException: Unsupported URI schema: 'fmu-proxy' in URI: 'fmu-proxy://localhost:9090?guid=b71f76f7-b51e-40d5-affb-f63905622e2b' . Supported schemas are: [file, fmuproxy] at com.opensimulationplatform.systemstructure.util.DefaultOspModelDescriptionLocator.get(DefaultOspModelDescriptionLocator.java:58) at com.opensimulationplatform.cli.Validator.getModelDescriptionErrorMessages(Validator.java:93) at com.opensimulationplatform.cli.Validator.validate(Validator.java:48) at com.opensimulationplatform.cli.Main.main(Main.java:79) Caused by: java.lang.RuntimeException: Unsupported URI schema: 'fmu-proxy' in URI: 'fmu-proxy://localhost:9090?guid=b71f76f7-b51e-40d5-affb-f63905622e2b' . Supported schemas are: [file, fmuproxy]

@THEvang THEvang added the bug Something isn't working label Jun 22, 2020
@THEvang
Copy link
Member Author

THEvang commented Jun 22, 2020

I think the issue is here:

In the config files I have received, FMU Proxy is spelled fmu-proxy, not fmuproxy.

@THEvang THEvang self-assigned this Jun 22, 2020
@THEvang
Copy link
Member Author

THEvang commented Jun 22, 2020

@THEvang
Copy link
Member Author

THEvang commented Jun 22, 2020

In the above example, there is also the issue of specifying the FMU by GUID and not by name. I don't think the osp-validator is able to find the FMUs modelDescription based on ID. Looks like it uses the name of the FMU.

@ljamt
Copy link
Member

ljamt commented Sep 27, 2021

@THEvang, I assume this issue can be closed as it's fixed?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants