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

Reduction GUI writes files in the home directory #11709

Closed
mantid-builder opened this issue Jan 9, 2015 · 4 comments
Closed

Reduction GUI writes files in the home directory #11709

mantid-builder opened this issue Jan 9, 2015 · 4 comments
Assignees
Labels
Framework Issues and pull requests related to components in the Framework 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

@mantid-builder
Copy link
Collaborator

This issue was originally TRAC 10867

Original Reporter: @FedeMPouzols

I just saw that I have a couple of .mantid_... files in my home:

  • .mantid_data_sets
  • .mantid_last_HFIR_reduction.xml

Maybe there's a good reason for that, but I'd say that these files would be happier in the directory where other mantid files are written, ~/.mantid (bin on Windows), possibly inside subdirectories specific to different interfaces.

You can quickly find where this is done with a grep for the following data members:

  • ERROR_REPORT_DIR
  • LAST_REDUCTION_NAME
  • or more in general, calls to "path.expanduser"
    It seems that the reduction GUI uses the home directory in a few places, and it also seems that this doesn't happen in the other interfaces or anywhere else in the Mantid code.
@mantid-builder
Copy link
Collaborator Author

@NickDraper (2015-04-27T08:10:35):
Moved to R3.5 at the R3.4 code freeze

@mantid-builder mantid-builder added Low Priority Things that you don't ever want to be done. Framework Issues and pull requests related to components in the Framework labels Jun 3, 2015
@mantid-builder mantid-builder added this to the Release 3.5 milestone Jun 3, 2015
NickDraper added a commit that referenced this issue Jun 5, 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
Copy link
Contributor

It looks like this is primarily in some of the SNS and HIFR interfaces, you might want to check and assign on.

@NickDraper NickDraper modified the milestones: Release 3.7, Release 3.8 May 20, 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
@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
Framework Issues and pull requests related to components in the Framework 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

3 participants