Skip to content
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

Create an algorithm to save a series of contour plots as a video #12269

Closed
DanNixon opened this issue Mar 25, 2015 · 3 comments
Closed

Create an algorithm to save a series of contour plots as a video #12269

DanNixon opened this issue Mar 25, 2015 · 3 comments
Assignees
Labels
Indirect/Inelastic Issues and pull requests related to indirect or inelastic Low Priority Things that you don't ever want to be done. Stale This label is automatically applied to issues that are automatically closed by the stale bot

Comments

@DanNixon
Copy link
Member

This issue was originally TRAC 11430

Given some matrix workspaces (as a WorkspaceGroup) create a contour plot for each and output them as a video file with a given delay between each frame.

There should be support for adding log values as annotations to the frames, putting several plots side by side and normalising the data to the first dataset in the group.

For now this will just be a script.

@DanNixon
Copy link
Member Author

@DanNixon (2015-04-10T10:15:50):
An initial version of the script is here: https://github.com/mantidproject/scripts/blob/master/development/inelastic/colour_plot_timelapse.py

This does everything (with the exception of side by side plots) that the script needs to.

It can be tested using the data in Babylon5/DanNixon/osiris_scan


@NickDraper (2015-04-27T08:38:42):
At the moment the script runs, but does not appear to create a video (at least on windows).

This needs better documentation for setting up an environment where it will work.

For example is it linux only? Can it be run on windows if ffmepg is installed, and where does it need to be installed?

@DanNixon DanNixon added the Indirect/Inelastic Issues and pull requests related to indirect or inelastic label Jun 3, 2015
@DanNixon DanNixon self-assigned this Jun 3, 2015
@DanNixon DanNixon added this to the Release 3.5 milestone Jun 3, 2015
@DanNixon DanNixon assigned ElliotAOram and unassigned DanNixon Jul 30, 2015
@NickDraper NickDraper modified the milestones: Release 3.5, Release 3.6 Sep 14, 2015
@NickDraper NickDraper modified the milestones: Release 3.6, Release 3.7 Jan 22, 2016
@NickDraper NickDraper modified the milestones: Release 3.7, Release 3.8 May 20, 2016
@ElliotAOram ElliotAOram added the Low Priority Things that you don't ever want to be done. label Aug 10, 2016
@NickDraper NickDraper modified the milestones: Release 3.8, Release 3.9 Oct 3, 2016
@NickDraper NickDraper modified the milestones: Release 3.9, Temporary Holding Oct 14, 2016
@louisemccann louisemccann removed their assignment Aug 16, 2017
@NickDraper NickDraper removed this from the Temporary Holding milestone Oct 3, 2017
@stale
Copy link

stale bot commented Feb 23, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. If you feel this is incorrect please comment to keep it alive, with a reason why.

To prevent closure, e.g. for long-term planning issues, add the "Never Stale" label.

@stale stale bot added the Stale This label is automatically applied to issues that are automatically closed by the stale bot label Feb 23, 2021
@stale
Copy link

stale bot commented Mar 2, 2021

This issue has been closed automatically. If this still affects you please re-open this issue with a comment so we can look into resolving it.

@stale stale bot closed this as completed Mar 2, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Indirect/Inelastic Issues and pull requests related to indirect or inelastic Low Priority Things that you don't ever want to be done. Stale This label is automatically applied to issues that are automatically closed by the stale bot
Projects
None yet
Development

No branches or pull requests

5 participants