I installed JuliaPro on my Windows 10 Desktop. Whenever I open JuliaPro, I see a deprecation warning though I have not coded anything.
Please find the below image, for more details.
Will it be a problem if I disable juno-julia-run package?
I had the same problem, found an answer in discord.
You should write something and save it as .jl file and then restrart Atom.
The problem would have solved by then
Related
I installed Scilab 5.5.2 on Windows 10, and then installed the Scilab Code Generator toolbox.
However, when I start Scilab, the following message appears and I can't use the toolbox. This problem occurs for every toolbox.
Start Scilab Code Generator
Version: 0.9.20190122
Load macros
atomsLoad: An error occurred while loading 'xcos_code_generator-0.9.20190122':
File "C:\Users\光\AppData\Roaming\Scilab\SCILAB~1.2\atoms\x64\XCOS_C~1\09E129~1.201\macros\names" does not exist or read access denied.
(光 is my username.)
I suppose the problem comes from "\Scilab\SCILAB~1.2" in the middle of the file path. In my computer, the only folder in "Scilab" is "scilab-5.5.2", so indeed the software cannot find the file it's looking for.
Does anyone have any ideas?
I need to use the toolbox at work soon, so any help is greatly appreciated. Thank you in advance.
Note: I'm not using the latest Scilab 6.0.2 because it fails to work on my computer. It closes immediately after I open it.
I solved the problem by myself.
It was my user name "光" that caused the problem. I found people saying that user names in full-width characters such as Japanese sometimes cause problems like this.
The solution is to create another user account with a name in half-width characters and install Scilab in that account. (Just changing the full-width user name doesn't work because it doesn't change the filenames that already exist.)
I couldn't find the solution until today because I was searching for solutions only in the context of Scilab, not in the context of software in general.
I hope this answer helps someone.
I'm not sure why you are using an outdated version of Scilab. The latest version is 6.0.2 on Windows. If the newer version doesn't work properly then that's the problem you need to fix first. To test your Scilab installation you may run it in the terminal. Find the installation folder. For me, it is C:\Program Files\scilab-6.0.2\bin the on cmd go to the path and run Scilex.exe. If not uninstall everything and install it in a proper way. My recommendation is to uninstall the old Scilab you already have. Then:
Install Chocolatey package manager
Open PowerShell as Admin and run choco update all -y, once in a while update your packages this way.
run choco install Scilab -y
then open the Scilab software
run the atomsInstall("xcos_code_generator") in the console
runt the atomsLoad("xcos_code_generator") to make sure your package is installed properly. You should see this as a result:
--> atomsInstall("xcos_code_generator")
Scanning repository http://atoms.scilab.org/6.0 ... Done
ans =
!xcos_code_generator 0.9.201901 user SCIHOME\atoms\x64\xcos_code_generator\0.9.201901 I !
--> atomsLoad("xcos_code_generator");
Start Scilab Code Generator
Version: 0.9.20190122
Load macros
Load help
Load demos
When I run the code given in the document on combined aero and structure I go this error:
AttributeError: 'module' object has no attribute 'matlib'
Based on the previous answer I had got, I tried to install the updated version of 'matplotlib' , but this has not solved the problem. Any help will greatly help me as I am a FORTRAN era person and a new convert to Python.
It looks like you're trying to use an intel compiled version of python and numpy can't find an necessary underlying library. Something is messed up in your python/numpy install.
This has nothing to do with OpenAeroStruct or OpenMDAO. If you can't fix your install, I suggest trying out the Anaconda python distribution, which should have everything precompiled correctly.
I don't have enough rep to comment, but please view this answer as a comment and I'll edit it once I can answer more properly.
That sounds like a numpy installation issue. Could you please post the entire error trace that you get when you try running the command?
Additionally, what system are you on (Windows, Mac, Linux), how did you install Python, and have you tried any other Python-based code that you can get to work successfully?
Edit: the most recent version of OpenAeroStruct has been modified to avoid this issue altogether.
I installed linter-php and also tried to configure it in config.cson as following
"linter-php":
executablePath: "C:\xampp\php"
but I don't see any indication that something that is related to linter affects atom display. How can I verify that this package (or any package in general) is working properly when atom is running?
To answer your question: you can find all active packages by running atom.packages.activePackages in Atom's developer console.
However, your problem could be caused by providing an invalid path. Backslashes need to be escaped in CSON, so your config should look like this:
"linter-php":
executablePath: "C:\\xampp\\php"
I'm re-running some R Markdown scripts that worked fine a month ago, but now kable_as_image is unable to find Ghostscript (yes, I'm on Windows 8). I get the following error message:
Error in kable_as_image(criteria.table,"Criteria",file_format="jpeg"):
Ghostscript is required to read PDF on windows. Please download it here: https://ghostscript.com/
My computer still has Ghostscript, which runs fine when I open it up independently (I tried reinstalling Ghostscript; it didn't help). My guess is that the problem has something to do with R, RStudio, or a package being unable to find the Ghostscript.
I'm pretty sure I've upgraded R in the interim, and I'm currently on 3.4.3 with the latest versions of kableExtra and magick. I've also tried
Sys.setenv(R_GSCMD="C:/Program Files/gs/gs9.22/bin/gswin64.exe")
(and also for gswin64c.exe) but that didn't help, either. Any advice would be appreciated.
Despite what the error message says, R needs the path to MikTeX (or your TeX program of choice), not to Ghostscript itself. The best solution is to add it to PATH in your operating system directly so it's always there, but it also works to add it within R. This is helpful to test it out before digging into your OS (make sure you have the right path), or if you don't have administrator privileges to your work machine.
Sys.setenv("PATH"=sprintf("%s;C:\\Users\\me\\AppData\\Local\\Programs\\MiKTeX 2.9\\miktex\\bin\\x64\\",Sys.getenv("PATH")))
Your path to MikTeX will likely be different than mine. Note that you need sprintf() or something similar to add the directory to the end of the PATH instead of overwriting the existing path.
I installed Atom and uber-juno as instructed by Julia's homepage, but when I tried to start Julia in Atom, I was given the following error:
ERROR: LoadError: ArgumentError: Juno not found in path
in require at loading.jl:249
in include at boot.jl:261
in include_from_node1 at loading.jl:320
in process_options at client.jl:280
in _start at client.jl:378
while loading C:\Users\think\.atom\packages\julia-client\script\boot.jl, in expression starting on line 36
I think you are doing using Juno inside Atom. Juno.jl is a separate package for developing Juno plugins.
Fist save a new file with a .jl extension and type some Julia code (or open an existing .jl file) in Atom, then press SHIFT + ENTER with the cursor in the block of code that you want to evaluate, you should see the result, ie.
1 + 1 # type SHIFT + ENTER
A bubble notification will pop up with the value 2 (when you just start Atom you will see a spinning gear icon until Juno is ready to evaluate a block of code).
This isn't really a question for StackOverflow, it's a package/installation discussion. There was a new version tagged this morning which makes use of the new Juno.jl package where the front end stuff is held (this will be useful for package developers since it will allow them to extend Juno / add extra functionality for their packages which interact with Juno, adding only a light dependency). However, Juno.jl is not yet a registered package, leading to this mess.
One way to deal with this problem is to install the development version of the package:
Pkg.clone("https://github.com/JunoLab/Juno.jl")
However, this is not recommended for most users since you'll be at the bleeding edge (you may also need to do [Pkg.checkout(x) for x in ["Media", "Blink", "Atom"]] and use the dev install. So while this would fix this for right now, this will put you on the bleeding edge, a version which does not have a guarantee of stability. Thus, don't do this unless you're really familiar with Julia. (If you didn't see this error and immediately know to check Github for Juno.jl and use Pkg.clone, then you likely shouldn't be using this solution because you will get many random errors coming up all the time due to being on the development version!)
Otherwise, wait for the fix. This error is known, someone opened the issue here. The standard uber-juno install should be fixed up shortly.
If you want more help see the Juno Gitter or the Juno discussion board.
I just re-installed Atom and ran into the same problem. The problem comes from line 31 of ~/.atom/package/julia-client/script/boot.jl which is using Juno. Comment out this line and then Packages > Julia > Start Julia works.
The best solution is to uninstall and reinstall package julia-client and uber-juno.