(OpenSourceAWEComponents) pkg> up
Updating registry at `~/.julia/registries/DyadRegistry.toml`
Updating registry at `~/.julia/registries/General.toml`
Updating registry at `~/.julia/registries/JSMLComponents.toml`
Updating registry at `~/.julia/registries/JuliaComputingRegistry.toml`
Updating registry at `~/.julia/registries/JuliaHubRegistry.toml`
Cloning [99806f68-afab-45ca-9d8c-ceff6bc61f54] DyadInterface from https://github.com/JuliaComputing/DyadInterface.jl.git
ERROR: failed to clone from https://github.com/JuliaComputing/DyadInterface.jl.git, error: GitError(Code:ERROR, Class:HTTP, unexpected http status code: 404)
Dyad looks promising. It is not clear to me whether the full scope of MTK possibilities are available in Dyad yet (SDEs, PDEs, etc.).
I am curious about the followingâŚ
With the Dyad Studio extension in VSCode, I understand that I can work with Dyad models locally on my laptop.
Does this also include that I can use the Dyad GUI locally on my laptop (or office desktop)?
If I at some stage (after I master Dyad Studio myself) want to include Dyad in my course, is there a procedure for giving students (could be many) access to installing Dyad Studio? Is this trust based, or would the university be asked to provide a list of students?
The problem is that it is looking for https://github.com/JuliaComputing/DyadInterface.jl.git when it should be looking for git@github.com:DyadLang/DyadInterface.jl.git. I have no idea why that is happening⌠Can you share ]registry st and ]st? Itâs probably best to follow up at GitHub ¡ Where software is built since then it will be tracked and not potentially lost in the middle of a fairly long thread.
They are not. MTK will continue to have things outside of the normal industrial use cases, while Dyad will be focused directly on giving a smooth industrial modeling workflow.
Not at this time.
They can just install the VS Code extension and they are off to the races!
Try with JULIA_PKG_SERVER=juliahub.com JULIA_PKG_USE_CLI_GIT=true julia --project=.; that may help (let us know if it indeed does so we update the FAQ!
If itâs not that, could you share ~/.gitconfig (minus any secrets) Does it have any rule like
@ufechner7 could you also confirm which version of Dyad Studio is installed on your machine? It should be v0.5.1. You would also have to launch Julia via the Julia: Start REPL command in VSCode (through the command palette) or as @pankgeorg mentioned by explicitly setting the package server via environment variable.
I will never ever do that. It does a lot things automatically, but never what I want. I prefer a small script run_julia in the bin folder that start Julia with all the options I need.
That works too In this case the only thing you need to set is the JULIA_PKG_SERVER environment variable. The workflow also assumes you have Revise loaded.
Pardon my ignorance, but what is meant by âhardware engineeringâ ?
In my context, this would imply VHDL or Verilog. I wondered for a moment whether Dyad is meant to facilitate FPGA engineering, competing with systems like Chisel, Clash, or HardCaml. But the only non-CPU hardware the documentation mentions is GPUs.
I see that thereâs an intent to be able to âgenerate code for embedded devicesâ. Are you able to specify what is meant by âembedded devicesâ ? Itâs an unfortunately blurry term and I understand if youâd rather not.
Iâm currently working on compiling ODEs from Julia to Verilog, is why Iâm asking all this.
Hardware engineering, like the creation of airplanes, cars, wind turbines, etc. Machines. And for embedded, itâs embedded controllers, like the controllers in airplanes and automobiles. VHDL and Verliog is more the microchip world which is different. The domain weâre talking about here is Modelica, Simulink, Amesim, etc.
TypeScript was chosen because we want the language kernel to run natively in a browser and in VS Code. As Chris points out, we arenât doing any math (numerical or symbolic) in the Dyad kernel, just semantic processing of the language itself and then code generation to Julia. MTK + Julia pick things up from there and do a lot of the computational heavy lifting.
ERROR: Unsatisfiable requirements detected for package DyadEcosystemDependencies [7bc808db]:
DyadEcosystemDependencies [7bc808db] log:
ââpossible versions are: 0.7.0-0.9.4 or uninstalled
âârestricted to versions 0.9.4 by TestComponent [aecf22dd], leaving only versions: 0.9.4
â ââTestComponent [aecf22dd] log:
â ââpossible versions are: 0.1.0 or uninstalled
â ââTestComponent [aecf22dd] is fixed to version 0.1.0
âârestricted by julia compatibility requirements to versions: uninstalled â no versions left
Although Pkg.status() doesnât give me version info of pkgs, but I believe they are correct