-
Notifications
You must be signed in to change notification settings - Fork 66
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
The built-in cinema viewer page: cinema_databases/cinema_out/index.html appears disorganized and unresponsive #1391
Comments
It seems like the output is malformed -- extra text should not be there. Not sure why that is happening. The pages are created to avoid need for a webserver, so it should not matter if server is used or not. We will check out cinema output routines. |
@devilkingsatan666 I've duplicated this bug and it is definitely a weird one. For some reason all of the text from the cinema files are being appended to index.html. As a temporary workaround, if you copy a clean version of index.html or delete all the appended text (after the end of the html block on line 56), you should be able to view your database in the browser. https://github.com/Alpine-DAV/ascent/blob/c11da70c958bd9cdcc5d49eacbbc13c95a48ecef/src/libs/ascent/web_clients/cinema/index.html Thanks for bringing this to our attention. |
@nicolemarsaglia @cyrush, Thank you so much for your great help! After implementing your suggestions, I can view the database correctly now! I explored the database elegantly via Visual Studio Code's "Live Server" plugin, as shown in the following image. Thank you so much!
|
Looks like a bug in one of our main dependencies. An issue ticket with a reproducer has been opened: LLNL/conduit#1326 Current workaround is to edit the generated files or copy/download clean files from here after using cinema: https://github.com/Alpine-DAV/ascent/tree/c11da70c958bd9cdcc5d49eacbbc13c95a48ecef/src/libs/ascent/web_clients/cinema |
Ascent develop has a fix as of #1425 |
I successfully generated a cinema database following the WarpX Ascent In-Situ Tutorial, using WarpX version 24.09, instrumented with Ascent version 0.9.3, built using Spack. I modified the Spack recipe for AMReX to include Ascent and Conduit as variants.
However, as shown in the attached screenshots, the cinema viewer web page created alongside the database (located at cinema_databases/cinema_out/index.html) appears disorganized and unresponsive regardless of whether the page is served via a web server.
Best regards,
Wu-Cheng Chiang
National Central University, Taiwan (R.O.C.)
The text was updated successfully, but these errors were encountered: