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

LoadSINQ should also work on windows #11569

Closed
MichaelWedel opened this issue Dec 9, 2014 · 2 comments
Closed

LoadSINQ should also work on windows #11569

MichaelWedel opened this issue Dec 9, 2014 · 2 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

@MichaelWedel
Copy link
Contributor

This issue was originally TRAC 10727

The LoadSINQ algorithm loads PSI SINQ data automatically from the AFS-storage, which works well in Linux environments. In Windows environments this works also, provided the appropriate directories are added to the data search path. The problem is, that this makes it necessary to add a lot of directories (for each instrument, for each year, each group of files, ...). I would like to modify LoadSINQ so that it's enough to add the top level directory where all SINQ data are located.


Keywords: SINQ

@MichaelWedel MichaelWedel added the Framework Issues and pull requests related to components in the Framework label Jun 3, 2015
@MichaelWedel MichaelWedel self-assigned this Jun 3, 2015
@MichaelWedel MichaelWedel added this to the Release 3.5 milestone Jun 3, 2015
NickDraper added a commit that referenced this issue Jun 5, 2015
NickDraper added a commit that referenced this issue Jun 5, 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
@MichaelWedel MichaelWedel added the Low Priority Things that you don't ever want to be done. label Sep 17, 2015
@NickDraper NickDraper modified the milestones: Release 3.6, Release 3.7 Jan 22, 2016
@MichaelWedel MichaelWedel modified the milestones: Release 3.7, Release 3.8 May 18, 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

2 participants