Live script: Error Loading

154 visualizaciones (últimos 30 días)
Toke Frederiksen
Toke Frederiksen el 17 de Mayo de 2017
Comentada: Eliza Sikorska el 6 de Mayo de 2022
Hi I have created a matlab livescript file, and saved it as .mlx . When i now try to open the file i get the error:
Error Loading "path to file"
I have tried opening it in a text editor, but it is just empty, though the file is 219 kb. What can I do?
  2 comentarios
pablo Jaramillo
pablo Jaramillo el 15 de En. de 2021
I tried @Ben Harris approach, but unfortunately did not work. While trying to opening the livescript in 7 zip, it wen to matlab and showed the same error.
Luckily, this file was in my OneDrive folder so I could restore a previous version safely from the files options. I guess Google drive, dropbox and others have the same option..
Adam Danz
Adam Danz el 23 de Mayo de 2021
To add another data point, I fixed the problem by replacing a corrupted image file.
After unzipping the mlx file, the embedded image are stored in a folder named "media" and one of the images were missing (image3). I had a copy of the image, renamed it "image3.gif", and added it to the folder.

Iniciar sesión para comentar.

Respuestas (4)

James Johnson
James Johnson el 15 de Feb. de 2020
One workaround I found is to do a file comparison. Create an empy .mlx file and compare it to the one that MATLAB failed to handle properly. Then you can "merge" the code into the empty file. In my case MATLAB was able to do the diff just not load the file with the plots and prints statements. They should really have an option to load a Live Script WITHOUT the plotting etc.
In my situation the live script hung, returning control of MATLAB to me but nonetheless indicating it was still running and not displaying anything. I closed MATLAB using the "exit" command and restarted MATLAB, but the file wouldn't load. MATLAB just showed the loading wheel and eventually displayed an uninformative error message. I think the problem was something with the display buffer since my code was printing thousands of warnings and was plotting things on top of one another. I added "drawnow" after every plot. Silenced the warning, and put pause(0.1) at the end of every section.
  1 comentario
Daniel Renjewski
Daniel Renjewski el 30 de Mzo. de 2020
Worked for me - thanks for the hint. It saved my day!

Iniciar sesión para comentar.


Ben Harris
Ben Harris el 27 de Abr. de 2020
I have been able to recover from a broken Live Script. Basically, my live script file was corrupted from an abnormal termination of MATLAB. When I tried to load the live script, I was able to see my live script code to pop up, but after the code displayed, I got the "Error Loading ...." popup.
Here was the fix.
This was how I diagnosed the problem. I opened up the live script (the mlx file) with unzip from the command prompt. The mlx file acted like a zip file as far as unzip cared. A directory tree was created. In the "matlab" subdirectory. I saw the output.xml file was enormous and likely corrupt.
This is how I fixed my corrupted mlx file. I created a blank mlx file in MATLAB. Then I used 7 zip to open up the blank mlx file, and copy the contents of its output.xml file. So I had the "fresh" output ready to paste on the clipboard. I then again used 7 zip to open up my corrupted mlx file and I edited its output.xml. I did a "select all" in the editor and replaced it with the fresh output.from the clipboard. I saved it. 7 zip asked me to confirm if I was sure I wanted to update the archive and I said yes. And voila, I was able to open the corrupted mlx file.
Now here's the rub: I had to fix what the live script was doing before I ran it again. The corruption of the output.xml occured because of the abnormal termination of MATLAB. That happened because I pushed the limits of an ODE solver too far and it was generating so many error messages that the link between the UI and the backend of MATLAB got detached. That is why I suspect MATLAB hung. So I did not want another such hang. I had to loosen the tolerance I was using in the ODE solver.
  4 comentarios
Wu Yu-Wei
Wu Yu-Wei el 25 de Sept. de 2020
Yes, I am. Also I am able to see the output.xml of the blank file. But if I try to do the same for my .mlx file, I am getting an error. I have added a screenshot below of the error message.
Ethan Duckworth
Ethan Duckworth el 6 de Mzo. de 2021
Editada: Ethan Duckworth el 6 de Mzo. de 2021
Thanks to Ben Harris! I mentioned using his fix/approach using Emacs on Mac OSX in another post

Iniciar sesión para comentar.


Dimitris Iliou
Dimitris Iliou el 19 de Mayo de 2017
I think the reason you are getting this error is possibly because the .mlx file becomes corrupted.
One thing I can suggest is using the 'Previous Versions' feature of Windows (if you can do that), in order to get a previous non-corrupted version of the file.
  2 comentarios
Ben Harris
Ben Harris el 27 de Abr. de 2020
Thank you for that important clue. I didn't have prior versions. But I was able to go into the mlx file with 7 zip and fix it. I submitted the fix description.
Eliza Sikorska
Eliza Sikorska el 6 de Mayo de 2022
Thank you so much!

Iniciar sesión para comentar.


Otto Hofstätter
Otto Hofstätter el 14 de Dic. de 2017
I solved the problem by opening the script with an older Matlab Version (2016). I copied the content to a normal script - and i leave the live script behind.

Categorías

Más información sobre Scripts en Help Center y File Exchange.

Etiquetas

Community Treasure Hunt

Find the treasures in MATLAB Central and discover how the community can help you!

Start Hunting!

Translated by