This pull request removes Git tracking of the "linz" directory and everything in it. These scripts formed the basis of most of my FOXSI analysis work for a long time and were originally included in the git repository so that others could use my scripts as examples. However, with the growing number of people using our code, my infrequent (but occasional) updates of these scripts, and my desire to reorganize my own directory structure, I'd like to remove tracking of this directory.
Direct consequences: once this directory is gone, these scripts will no longer appear in your directory. No procedures in other sections of the code should be depending on these, so there should be no impact on your own analysis. If you would like to retain the examples for future use, I suggest that you make a copy of this directory and store it somewhere on your computer. As a last resort, you can always page through the GitHub repository history to find a file.
Let's discuss this at the Wednesday foxsi-science meeting, but I'd specifically like input from @jtvievering @somusset @athrayspanchap @pymilo @smusset since they may be the most impacted.
This pull request removes Git tracking of the "linz" directory and everything in it. These scripts formed the basis of most of my FOXSI analysis work for a long time and were originally included in the git repository so that others could use my scripts as examples. However, with the growing number of people using our code, my infrequent (but occasional) updates of these scripts, and my desire to reorganize my own directory structure, I'd like to remove tracking of this directory.
Direct consequences: once this directory is gone, these scripts will no longer appear in your directory. No procedures in other sections of the code should be depending on these, so there should be no impact on your own analysis. If you would like to retain the examples for future use, I suggest that you make a copy of this directory and store it somewhere on your computer. As a last resort, you can always page through the GitHub repository history to find a file.
Let's discuss this at the Wednesday foxsi-science meeting, but I'd specifically like input from @jtvievering @somusset @athrayspanchap @pymilo @smusset since they may be the most impacted.