NAN GUI loses track of user - Revision history

Mmaciejewski at 15:44, 23 June 2025

2025-06-23T15:44:50Z

← Older revision		Revision as of 15:44, 23 June 2025
Line 20:		Line 20:

	'''Important:''' If a dataset was already harvested under the unspecified username, the Manual Harvest window will issue a warning. In this case, it is strongly recommended that you contact your facility manager to reassign the dataset, rather than forcing a manual transfer, to avoid creating duplicate entries in the system.		'''Important:''' If a dataset was already harvested under the unspecified username, the Manual Harvest window will issue a warning. In this case, it is strongly recommended that you contact your facility manager to reassign the dataset, rather than forcing a manual transfer, to avoid creating duplicate entries in the system.

			[[Category:FAQ]]

Mmaciejewski at 15:44, 23 June 2025

2025-06-23T15:44:21Z

← Older revision		Revision as of 15:44, 23 June 2025
Line 6:		Line 6:
	You can identify this condition in several ways:		You can identify this condition in several ways:

	* The NDTS daemon log file will report that contact with the GUI was lost for 50 seconds and that it is defaulting to the unspecified user's NDTS harvesting settings.		* The [[NDTS Daemon Operation#(C) Daemon Logging\|'''NDTS daemon log file''']] will report that contact with the GUI was lost for 50 seconds and that it is defaulting to the unspecified user's NDTS harvesting settings.
	* In the NDTS GUI, select '''[[NDTS-GUI#NDTS Experimental Details Window\|Enter Experiment Details]]'''. This probes the daemon and shows the actual currently selected user. From there, you can re-select your NAN username, and the GUI will update accordingly.		* In the NDTS GUI, select '''[[NDTS-GUI#NDTS Experimental Details Window\|Enter Experiment Details]]'''. This probes the daemon and shows the actual currently selected user. From there, you can re-select your NAN username, and the GUI will update accordingly.
	* The NDTS audit file will log the experiment endings, whether they were harvested (based on the unspecified user defaults), and that the NAN user was "unspecified".		* The [[NDTS Daemon Operation#(B) Experiment Transfer Audit File\|'''NDTS audit file''']] will log the experiment endings, whether they were harvested (based on the unspecified user defaults), and that the NAN user was "unspecified".

	=== How to correct the situation? ===		=== How to correct the situation? ===

Mmaciejewski at 15:41, 23 June 2025

2025-06-23T15:41:56Z

← Older revision		Revision as of 15:41, 23 June 2025
Line 1:		Line 1:
	The [[NDTS-GUI#NDTS-GUI Main Window\|~~'''~~NDTS GUI'''~~]] shows~~ the currently selected NAN user ~~on the display~~, ~~but~~ it is the NDTS daemon that ~~is keeping track of~~ the ~~current~~ local workstation username and the selected NAN username. If the NDTS GUI loses communication with the NDTS daemon for an extended period ~~of time~~ (50 seconds) ~~than~~ the ~~NDTS~~ daemon will revert to an [[NAN Terminology\|~~'''~~unspecified user''']]. In ~~that circumstance~~ the NDTS GUI ~~can~~ become out-of-sync with the ~~NDTS~~ daemon. This ~~feature was added to ensure that~~ data ~~would not accidently be~~ harvested to the wrong user ~~by accident in the event that~~ the GUI loses ~~communication with~~ the daemon.		{{FAQReturn}}

			The '''[[NDTS-GUI#NDTS-GUI Main Window\|NDTS GUI]]''' displays the currently selected NAN user. However, it is the NDTS daemon that tracks the local workstation username and the selected NAN username. If the NDTS GUI loses communication with the NDTS daemon for an extended period (50 seconds), the daemon will revert to an '''[[NAN Terminology\|unspecified user]]'''. In this case, the NDTS GUI may become out of sync with the daemon. This safeguard prevents data from being mistakenly harvested under the wrong user if the GUI loses connection to the daemon.

	=== How do I know if this occurred? ===		=== How do I know if this occurred? ===
	~~The indicator that~~ this ~~occurred can be found~~ in ~~different locations~~:		You can identify this condition in several ways:

	* ~~In the~~ daemon log file it will ~~state~~ that ~~the daemon has lost~~ contact with the GUI for 50 seconds and that it is defaulting to unspecified ~~users~~ NDTS harvesting settings		* The NDTS daemon log file will report that contact with the GUI was lost for 50 seconds and that it is defaulting to the unspecified user's NDTS harvesting settings.
	* In the NDTS GUI select Enter Experiment Details ~~which will probe~~ the daemon and ~~show~~ the "actual" currently selected user. From there you can select ~~the correct~~ NAN ~~user~~ and ~~the front of~~ the GUI will update.		* In the NDTS GUI, select '''[[NDTS-GUI#NDTS Experimental Details Window\|Enter Experiment Details]]'''. This probes the daemon and shows the actual currently selected user. From there, you can re-select your NAN username, and the GUI will update accordingly.
	* ~~In the~~ NDTS audit file it will ~~show~~ the ~~experiments ending~~, whether they ~~are~~ harvested ~~or not~~ (based on the ~~unselected users~~ defaults), and ~~who~~ the NAN user ~~is (~~unspecified).		* The NDTS audit file will log the experiment endings, whether they were harvested (based on the unspecified user defaults), and that the NAN user was "unspecified".

	=== How to correct the situation? ===		=== How to correct the situation? ===
	~~From~~ the NDTS GUI ~~select the~~ [[NDTS-GUI#NDTS Experimental Details Window\|~~'''~~Enter Experiment Details'''~~]] button~~ and ~~from the panel~~ select your NAN username. All ~~further~~ datasets will be harvested ~~with~~ the ~~correct NAN~~ username.		In the NDTS GUI, click on '''[[NDTS-GUI#NDTS Experimental Details Window\|Enter Experiment Details]]''' and re-select your correct NAN username. All subsequent datasets will then be harvested under the proper username.

	=== How to get the missing datasets into my data browser? ===		=== How to get the missing datasets into my data browser? ===
	Datasets collected ~~in the faulted condition where~~ the user was unspecified ~~will be harvested,~~ or not harvested, depending on the [[Manage Facility Users#Unknown (unspecified) Users\|~~'''~~default settings for the unspecified user'''~~]] controlled~~ by the ~~NMR~~ facility manager.		Datasets collected while the user was unspecified may or may not have been harvested, depending on the '''[[Manage Facility Users#Unknown (unspecified) Users\|default settings for the unspecified user]]''' set by your NMR facility manager.

			* If the datasets were harvested — ask your facility manager to reassign them to your NAN user.
			* If the datasets were not harvested — log in to the NMR spectrometer workstation and use the '''[[NDTS-GUI#Manual Harvest Window\|Manual Harvest]]''' option in the NDTS GUI to select and harvest the missing datasets.

	* If the datasets were harvested - ask your facility manager to reassign the datasets to your NAN user		'''Important:''' If a dataset was already harvested under the unspecified username, the Manual Harvest window will issue a warning. In this case, it is strongly recommended that you contact your facility manager to reassign the dataset, rather than forcing a manual transfer, to avoid creating duplicate entries in the system.
	* If the datasets were not harvested - login in to the NMR spectrometer workstation and select [[NDTS-GUI#Manual Harvest Window\|'''~~Manual Harvest~~'''~~]] from the NDTS GUI to select the missing datasets and harvest them. Note that if the~~ dataset ~~has~~ already ~~been~~ harvested~~, but with~~ the unspecified username, the Manual Harvest ~~option~~ will ~~give you~~ a warning ~~that the dataset has already been harvested~~. In this case we strongly ~~encourage~~ you ~~to ask the~~ facility manager to ~~assign~~ the dataset ~~to you~~ rather than forcing ~~the~~ manual transfer to avoid duplicate ~~datasets~~ in the system.

Mmaciejewski at 15:31, 23 June 2025

2025-06-23T15:31:25Z

← Older revision		Revision as of 15:31, 23 June 2025
Line 1:		Line 1:
	The [[NDTS-GUI#NDTS-GUI Main Window\|NDTS GUI]] shows the currently selected NAN user on the display, but it is the NDTS daemon that is keeping track of the current local workstation username and the selected NAN username. If the NDTS GUI loses communication with the NDTS daemon for an extended period of time (50 seconds) than the NDTS daemon will revert to an unspecified user. In that circumstance the NDTS GUI can become out-of-sync with the NDTS daemon. This feature was added to ensure that data would not accidently be harvested to the wrong user by accident in the event that the GUI loses communication with the daemon.		The [[NDTS-GUI#NDTS-GUI Main Window\|'''NDTS GUI''']] shows the currently selected NAN user on the display, but it is the NDTS daemon that is keeping track of the current local workstation username and the selected NAN username. If the NDTS GUI loses communication with the NDTS daemon for an extended period of time (50 seconds) than the NDTS daemon will revert to an [[NAN Terminology\|'''unspecified user''']]. In that circumstance the NDTS GUI can become out-of-sync with the NDTS daemon. This feature was added to ensure that data would not accidently be harvested to the wrong user by accident in the event that the GUI loses communication with the daemon.

	=== How do I know if this occurred? ===		=== How do I know if this occurred? ===
Line 9:		Line 9:

	=== How to correct the situation? ===		=== How to correct the situation? ===
	~~Open~~ the Enter Experiment Details panel ~~and~~ select your NAN username. All further datasets will be harvested with the correct NAN username.		From the NDTS GUI select the [[NDTS-GUI#NDTS Experimental Details Window\|'''Enter Experiment Details''']] button and from the panel select your NAN username. All further datasets will be harvested with the correct NAN username.

	=== How to get the missing datasets into my data browser? ===		=== How to get the missing datasets into my data browser? ===
	Datasets collected in the faulted condition where the user was unspecified will be harvested, or not harvested, depending on the [[Manage Facility Users\|default settings for the unspecified user]] controlled by the NMR facility manager.		Datasets collected in the faulted condition where the user was unspecified will be harvested, or not harvested, depending on the [[Manage Facility Users#Unknown (unspecified) Users\|'''default settings for the unspecified user''']] controlled by the NMR facility manager.

	If the datasets were harvested - ask your facility manager to reassign the datasets to your NAN user		* If the datasets were harvested - ask your facility manager to reassign the datasets to your NAN user
			* If the datasets were not harvested - login in to the NMR spectrometer workstation and select [[NDTS-GUI#Manual Harvest Window\|'''Manual Harvest''']] from the NDTS GUI to select the missing datasets and harvest them. Note that if the dataset has already been harvested, but with the unspecified username, the Manual Harvest option will give you a warning that the dataset has already been harvested. In this case we strongly encourage you to ask the facility manager to assign the dataset to you rather than forcing the manual transfer to avoid duplicate datasets in the system.
	If the datasets were not harvested - login in the NMR spectrometer workstation and select Manual Harvest from the NDTS GUI to select the missing datasets and harvest them. Note that if the dataset has already been harvested, but with the unspecified username, the Manual Harvest option will give you a warning that the dataset has already been harvested. In this case we strongly encourage you to ask the facility manager to assign the dataset to you rather than forcing the manual transfer to avoid duplicate datasets in the system.

Mmaciejewski at 15:22, 23 June 2025

2025-06-23T15:22:34Z

← Older revision		Revision as of 15:22, 23 June 2025
Line 1:		Line 1:
	The NAN GUI ~~shows~~ the currently selected NAN user		The [[NDTS-GUI#NDTS-GUI Main Window\|NDTS GUI]] shows the currently selected NAN user on the display, but it is the NDTS daemon that is keeping track of the current local workstation username and the selected NAN username. If the NDTS GUI loses communication with the NDTS daemon for an extended period of time (50 seconds) than the NDTS daemon will revert to an unspecified user. In that circumstance the NDTS GUI can become out-of-sync with the NDTS daemon. This feature was added to ensure that data would not accidently be harvested to the wrong user by accident in the event that the GUI loses communication with the daemon.

			=== How do I know if this occurred? ===
			The indicator that this occurred can be found in different locations:

			* In the daemon log file it will state that the daemon has lost contact with the GUI for 50 seconds and that it is defaulting to unspecified users NDTS harvesting settings
			* In the NDTS GUI select Enter Experiment Details which will probe the daemon and show the "actual" currently selected user. From there you can select the correct NAN user and the front of the GUI will update.
			* In the NDTS audit file it will show the experiments ending, whether they are harvested or not (based on the unselected users defaults), and who the NAN user is (unspecified).

			=== How to correct the situation? ===
			Open the Enter Experiment Details panel and select your NAN username. All further datasets will be harvested with the correct NAN username.

			=== How to get the missing datasets into my data browser? ===
			Datasets collected in the faulted condition where the user was unspecified will be harvested, or not harvested, depending on the [[Manage Facility Users\|default settings for the unspecified user]] controlled by the NMR facility manager.

			If the datasets were harvested - ask your facility manager to reassign the datasets to your NAN user

			If the datasets were not harvested - login in the NMR spectrometer workstation and select Manual Harvest from the NDTS GUI to select the missing datasets and harvest them. Note that if the dataset has already been harvested, but with the unspecified username, the Manual Harvest option will give you a warning that the dataset has already been harvested. In this case we strongly encourage you to ask the facility manager to assign the dataset to you rather than forcing the manual transfer to avoid duplicate datasets in the system.

Mmaciejewski: Created page with "The NAN GUI shows the currently selected NAN user"

2025-06-23T14:42:03Z

Created page with "The NAN GUI shows the currently selected NAN user"

New page

The NAN GUI shows the currently selected NAN user