You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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.
@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!
Best regards,
Wu-Cheng Chiang
National Central University, Taiwan (R.O.C.)
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: