Open
Conversation
| - mapped drive (`d:`) is not connected properly: often double clicking on the drive is enough to get it remapped | ||
| - mapped drive (`d:`) is not (re)connected properly: often double clicking on the drive is enough to get it remapped | ||
| - data is trying to copied to wrong cycle subdirectory - see not below about incorrect cycle. Look at `post_command*` log and check cycle number looks correct, it is read from `o:\setcycle.cmd`. As old cycles are mounted read-only you may see robocopy errors mentioning `The media is write protected` in this case. | ||
| - something else: fix and document here |
Member
There was a problem hiding this comment.
Suggested change
| - something else: fix and document here |
| - if all files are in the wrong cycle, either the central copy has not been updated, or the `o:` drive on the instrument has become disconnected so it is not being updated to the latest version. Try clicking on `o:` in windows explorer to reconnect it, and confirm the file `o:\setcycle.cmd` exists and contains the correct cycle number. | ||
|
|
||
| to reconnect the o: drive, log onto the NDX and just open it in windows explorer, that should reconnect using cached credentials. Then check that `o:\setcycle.cmd` has the correct cycle number. | ||
| to reconnect the o: drive, log onto the NDX and just open it in windows explorer, that should reconnect using cached credentials. Then check that `o:\setcycle.cmd` has the correct cycle number. We had one case recently where the `o:` mapping was incorrect and was missing the `instrument` subdirectory - the network drive mapping needed to be readded so `o:` pointed at the directory containing `setcycle.cmd` |
Member
There was a problem hiding this comment.
readability nits
Suggested change
| to reconnect the o: drive, log onto the NDX and just open it in windows explorer, that should reconnect using cached credentials. Then check that `o:\setcycle.cmd` has the correct cycle number. We had one case recently where the `o:` mapping was incorrect and was missing the `instrument` subdirectory - the network drive mapping needed to be readded so `o:` pointed at the directory containing `setcycle.cmd` | |
| To reconnect the `o:` drive, log on to the NDX and open the `o:` drive in windows explorer, which should reconnect using cached credentials. Then check that `o:\setcycle.cmd` has the correct cycle number. If the `o:` mapping is incorrect and is missing the `instrument` subdirectory, the network drive mapping needs to be readded so that `o:` points to the directory containing `setcycle.cmd`. |
GRyall
reviewed
Feb 19, 2026
|
|
||
| - mapped drive (`d:`) is not connected properly: often double clicking on the drive is enough to get it remapped | ||
| - mapped drive (`d:`) is not (re)connected properly: often double clicking on the drive is enough to get it remapped | ||
| - data is trying to copied to wrong cycle subdirectory - see not below about incorrect cycle. Look at `post_command*` log and check cycle number looks correct, it is read from `o:\setcycle.cmd`. As old cycles are mounted read-only you may see robocopy errors mentioning `The media is write protected` in this case. |
Member
There was a problem hiding this comment.
Suggested change
| - data is trying to copied to wrong cycle subdirectory - see not below about incorrect cycle. Look at `post_command*` log and check cycle number looks correct, it is read from `o:\setcycle.cmd`. As old cycles are mounted read-only you may see robocopy errors mentioning `The media is write protected` in this case. | |
| - it is attempting to copy data to the wrong cycle subdirectory - see note below about incorrect cycle. Look at `post_command*` log and check the cycle number looks correct, it is read from `o:\setcycle.cmd`. As old cycles are mounted read-only you may see robocopy errors mentioning `The media is write protected` in this case. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.