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
For now, I will add a button that allows to export a json file to save the current tree visualization, which will NOT re-use Re_run button to display the required visualization, but instead use specific functions for each one of the views imported through projects
Then it will be nice to link this with the INNUENDO platform in which a similar JSON post could be made to some url and trigger these events to show the required dataset.
The text was updated successfully, but these errors were encountered:
Now projects can be imported to pATLAS through this API. So the platform can use a similar object in the future. The projects object follows a certain structure:
By default everything is set to false but appending to mashscreen for instance can then trigger the importProject function (available in ./patlas/db_manager/db_app/static/js/projects/importProjects.js) like this:
importProject(typeOfProject,"mashscreen")
So, the idea would be to make something like the above function after receiving a post from elsewhere.
For now, I will add a button that allows to export a json file to save the current tree visualization, which will NOT re-use
Re_run
button to display the required visualization, but instead use specific functions for each one of the views imported through projectsThen it will be nice to link this with the INNUENDO platform in which a similar JSON post could be made to some url and trigger these events to show the required dataset.
The text was updated successfully, but these errors were encountered: