MEG Wiki - User contributions [en]

Squiggles research computer server

2025-04-21T15:23:24Z

Vahab: /* Troubleshooting */

=== Introduction ===
"Squiggles" is a dedicated research computer server tailored for the analysis and storage of MEG, Neurophysiology, and Epilepsy data. This guide outlines how to connect using either the recommended FastX connection or the traditional VNC method.

=== Access Requirements ===
==== RCC Account ====

* An RCC (Research Computer Server) account is necessary to access "Squiggles".
* Register for an account at [https://docs.rcc.mcw.edu/user-guide/accounts/ MCW-Infoscope's Research Computing Center].
* If prompted, select "others" and then "squiggles" to specify the server you wish to access.
* Account approval generally takes 1-3 days. For any issues, contact Help-RCC at <help-rcc@mcw.edu>.

=== Login to Squiggles ===
'''Choosing a User Port:''' Each user is allocated a specific port number. New users should pick a port number (##) not already in use:

{| class="wikitable"
|-
! scope="col"|User
! scope="col"|Port
|-
|Jeff Stout
|5910, 5911
|-
|Joe Heffernan
|5912
|-
|Manoj Raghavan
|5913, 5998, 5999
|-
|Candida Ustine
|5914
|-
|Chad Carlson
|5915
|-
|Chris Anderson
|5916
|-
|Serena Thompson
|5917
|-
|Patrick Bauer
|5918
|-
|Jeff Binder
|5919
|-
|Leo Fernandino
|5920
|-
|Lisa Conant
|5921
|-
|Aqil Izadysadr
|5922
|-
|Nick Guzowski
|5923
|-
|Zack Harper
|5924
|-
|Bill Gross
|5925
|-
|Michelle Kassel
|5926
|-
|Greg McQuestion
|5927
|-
|Monica Keith
|5928
|-
|Priyanka Shah
|5929
|-
|Setayesh Abiazi Shalmani
|5930
|-
|Vahab Youssof Zadeh
|5931
|-
|Songhee Kim
|5935
|-
|Rupesh Chikara
|5944
|-
|Cameron J Stewart
|5992
|}

===== SSH Tunneling =====
* '''PowerShell Method (Mac/Linux/Windows):''' In a bash shell, terminal, or Windows PowerShell, execute the following to set up an SSH tunnel for the VNC Viewer:
<code>ssh -L 59##:localhost:59## USER@squiggles.rcc.mcw.edu</code>
where USER is your rcc user account and ## is the selected port number

* '''PuTTY (Windows):'''
[https://www.chiark.greenend.org.uk/~sgtatham/putty/ Download PuTTY] for SSH tunneling and refer to the images below for configuration:

PuTTY is an open-source software used for SSH Tunneling (or SSH Port Forwarding).

[[File:Putty config1.PNG]]
[[File:Putty config2 tunnel.PNG]]

=== Starting a Session and Connecting to Squiggles ===
Ensure you've established an SSH tunnel before proceeding with either the VNC or FastX methods.

==== VNC Method (preferred) ====
* '''Creating & Accessing a VNC Session''':
** VNC sessions initialize automatically upon boot-up.
** If issues occur, manually initiate a session using: <code>vncserver :## -geometry 1900x1200</code>, where <code>##</code> is your specific port number.
** Access the session using the [[https://www.realvnc.com/en/connect/download/viewer/ RealVNC viewer]].
** Input <code>localhost:##</code> in the server address bar, where <code>##</code> corresponds to the last two digits of your port.

[[image:vncviewer.png]]



=== Troubleshooting ===
;'''Identifying Active Users'''
:To compile a list of users with active VNC sessions, which aids in monitoring current access to the VNC service, execute:
:<code>ls -l /tmp/.X11-unix</code>
:This information can be used to oversee session activity and ensure that resources are allocated efficiently.

;'''Terminating a VNC Session'''
:For situations where session termination is necessary, you can directly close a VNC session through the terminal or opt for manual termination if the direct method is insufficient. To directly terminate a session, use:
:<code>vncserver -kill :##</code>
:Replace <code>:##</code> with your session number.

;'''Manual Termination of the VNC'''
:For manual termination, proceed to remove the session files with:
:<code>rm -f /tmp/.X##-lock</code>
:<code>rm -f /tmp/.X11-unix/X##</code>
:Ensure to replace <code>X##</code> with the correct session identifier. This allows for removing stuck or unresponsive sessions that cannot be closed normally.

;'''Alternative Solution: when Manual Termination of the VNC does not work'''
:Use the following command, replacing <code><username></code> with the actual username:
:<code>ps -ef | grep <username></code>
:This will list all processes related to the specified user. You can then terminate unwanted sessions by killing the process IDs:
:<code>kill -9 <PID></code>
:Where <code><PID></code> is the process ID obtained from the previous command's output.

:Optional: To check the environment variables active during a VNC session, which can help in troubleshooting further issues, view the VNC environment log:
:<code>cat ~/vnc.log</code>

;'''VNC connection‑closed / black‑screen issue'''
:Anaconda’s base environment can interfere with VNC and close the session.
:Deactivate it after login:
:<code>conda deactivate</code>

;'''Disable Conda auto‑activation (so you don’t have to run <code>conda deactivate</code> each time)'''
:If you seldom need Conda inside VNC, turn off automatic activation:
:* Run <code>conda config --set auto_activate_base false</code> (this updates <code>~/.condarc</code>), **or**
:* Edit <code>~/.bashrc</code> and comment out / delete the line that calls <code>conda activate base</code>.
:After logging out and back in, Conda will stay inactive by default; activate it later with <code>conda activate <env></code> only when needed.

</pre>

Squiggles research computer server

2025-04-21T15:21:23Z

Vahab: /* Troubleshooting */

=== Introduction ===
"Squiggles" is a dedicated research computer server tailored for the analysis and storage of MEG, Neurophysiology, and Epilepsy data. This guide outlines how to connect using either the recommended FastX connection or the traditional VNC method.

=== Access Requirements ===
==== RCC Account ====

* An RCC (Research Computer Server) account is necessary to access "Squiggles".
* Register for an account at [https://docs.rcc.mcw.edu/user-guide/accounts/ MCW-Infoscope's Research Computing Center].
* If prompted, select "others" and then "squiggles" to specify the server you wish to access.
* Account approval generally takes 1-3 days. For any issues, contact Help-RCC at <help-rcc@mcw.edu>.

=== Login to Squiggles ===
'''Choosing a User Port:''' Each user is allocated a specific port number. New users should pick a port number (##) not already in use:

{| class="wikitable"
|-
! scope="col"|User
! scope="col"|Port
|-
|Jeff Stout
|5910, 5911
|-
|Joe Heffernan
|5912
|-
|Manoj Raghavan
|5913, 5998, 5999
|-
|Candida Ustine
|5914
|-
|Chad Carlson
|5915
|-
|Chris Anderson
|5916
|-
|Serena Thompson
|5917
|-
|Patrick Bauer
|5918
|-
|Jeff Binder
|5919
|-
|Leo Fernandino
|5920
|-
|Lisa Conant
|5921
|-
|Aqil Izadysadr
|5922
|-
|Nick Guzowski
|5923
|-
|Zack Harper
|5924
|-
|Bill Gross
|5925
|-
|Michelle Kassel
|5926
|-
|Greg McQuestion
|5927
|-
|Monica Keith
|5928
|-
|Priyanka Shah
|5929
|-
|Setayesh Abiazi Shalmani
|5930
|-
|Vahab Youssof Zadeh
|5931
|-
|Songhee Kim
|5935
|-
|Rupesh Chikara
|5944
|-
|Cameron J Stewart
|5992
|}

===== SSH Tunneling =====
* '''PowerShell Method (Mac/Linux/Windows):''' In a bash shell, terminal, or Windows PowerShell, execute the following to set up an SSH tunnel for the VNC Viewer:
<code>ssh -L 59##:localhost:59## USER@squiggles.rcc.mcw.edu</code>
where USER is your rcc user account and ## is the selected port number

* '''PuTTY (Windows):'''
[https://www.chiark.greenend.org.uk/~sgtatham/putty/ Download PuTTY] for SSH tunneling and refer to the images below for configuration:

PuTTY is an open-source software used for SSH Tunneling (or SSH Port Forwarding).

[[File:Putty config1.PNG]]
[[File:Putty config2 tunnel.PNG]]

=== Starting a Session and Connecting to Squiggles ===
Ensure you've established an SSH tunnel before proceeding with either the VNC or FastX methods.

==== VNC Method (preferred) ====
* '''Creating & Accessing a VNC Session''':
** VNC sessions initialize automatically upon boot-up.
** If issues occur, manually initiate a session using: <code>vncserver :## -geometry 1900x1200</code>, where <code>##</code> is your specific port number.
** Access the session using the [[https://www.realvnc.com/en/connect/download/viewer/ RealVNC viewer]].
** Input <code>localhost:##</code> in the server address bar, where <code>##</code> corresponds to the last two digits of your port.

[[image:vncviewer.png]]



=== Troubleshooting ===
;'''Identifying Active Users'''
:To compile a list of users with active VNC sessions, which aids in monitoring current access to the VNC service, execute:
:<code>ls -l /tmp/.X11-unix</code>
:This information can be used to oversee session activity and ensure that resources are allocated efficiently.

;'''Terminating a VNC Session'''
:For situations where session termination is necessary, you can directly close a VNC session through the terminal or opt for manual termination if the direct method is insufficient. To directly terminate a session, use:
:<code>vncserver -kill :xx</code>
:Replace <code>:xx</code> with your session number.

;'''Manual Termination of the VNC'''
:For manual termination, proceed to remove the session files with:
:<code>rm -f /tmp/.Xxx-lock</code>
:<code>rm -f /tmp/.X11-unix/Xxx</code>
:Ensure to replace <code>Xxx</code> with the correct session identifier. This allows for removing stuck or unresponsive sessions that cannot be closed normally.

;'''Alternative Solution: when Manual Termination of the VNC does not work'''
:Use the following command, replacing <code><username></code> with the actual username:
:<code>ps -ef | grep <username></code>
:This will list all processes related to the specified user. You can then terminate unwanted sessions by killing the process IDs:
:<code>kill -9 <PID></code>
:Where <code><PID></code> is the process ID obtained from the previous command's output.

:Optional: To check the environment variables active during a VNC session, which can help in troubleshooting further issues, view the VNC environment log:
:<code>cat ~/vnc.log</code>

;'''VNC connection‑closed / black‑screen issue'''
:Anaconda’s base environment can interfere with VNC and close the session.
:Deactivate it after login:
:<code>conda deactivate</code>

;'''Disable Conda auto‑activation (so you don’t have to run <code>conda deactivate</code> each time)'''
:If you seldom need Conda inside VNC, turn off automatic activation:
:* Run <code>conda config --set auto_activate_base false</code> (this updates <code>~/.condarc</code>), **or**
:* Edit <code>~/.bashrc</code> and comment out / delete the line that calls <code>conda activate base</code>.
:After logging out and back in, Conda will stay inactive by default; activate it later with <code>conda activate <env></code> only when needed.

</pre>

Squiggles research computer server

2025-04-04T21:42:34Z

Vahab: /* Login to Squiggles */

=== Introduction ===
"Squiggles" is a dedicated research computer server tailored for the analysis and storage of MEG, Neurophysiology, and Epilepsy data. This guide outlines how to connect using either the recommended FastX connection or the traditional VNC method.

=== Access Requirements ===
==== RCC Account ====

* An RCC (Research Computer Server) account is necessary to access "Squiggles".
* Register for an account at [https://docs.rcc.mcw.edu/user-guide/accounts/ MCW-Infoscope's Research Computing Center].
* If prompted, select "others" and then "squiggles" to specify the server you wish to access.
* Account approval generally takes 1-3 days. For any issues, contact Help-RCC at <help-rcc@mcw.edu>.

=== Login to Squiggles ===
'''Choosing a User Port:''' Each user is allocated a specific port number. New users should pick a port number (##) not already in use:

{| class="wikitable"
|-
! scope="col"|User
! scope="col"|Port
|-
|Jeff Stout
|5910, 5911
|-
|Joe Heffernan
|5912
|-
|Manoj Raghavan
|5913, 5998, 5999
|-
|Candida Ustine
|5914
|-
|Chad Carlson
|5915
|-
|Chris Anderson
|5916
|-
|Serena Thompson
|5917
|-
|Patrick Bauer
|5918
|-
|Jeff Binder
|5919
|-
|Leo Fernandino
|5920
|-
|Lisa Conant
|5921
|-
|Aqil Izadysadr
|5922
|-
|Nick Guzowski
|5923
|-
|Zack Harper
|5924
|-
|Bill Gross
|5925
|-
|Michelle Kassel
|5926
|-
|Greg McQuestion
|5927
|-
|Monica Keith
|5928
|-
|Priyanka Shah
|5929
|-
|Setayesh Abiazi Shalmani
|5930
|-
|Vahab Youssof Zadeh
|5931
|-
|Songhee Kim
|5935
|-
|Rupesh Chikara
|5944
|-
|Cameron J Stewart
|5992
|}

===== SSH Tunneling =====
* '''PowerShell Method (Mac/Linux/Windows):''' In a bash shell, terminal, or Windows PowerShell, execute the following to set up an SSH tunnel for the VNC Viewer:
<code>ssh -L 59##:localhost:59## USER@squiggles.rcc.mcw.edu</code>
where USER is your rcc user account and ## is the selected port number

* '''PuTTY (Windows):'''
[https://www.chiark.greenend.org.uk/~sgtatham/putty/ Download PuTTY] for SSH tunneling and refer to the images below for configuration:

PuTTY is an open-source software used for SSH Tunneling (or SSH Port Forwarding).

[[File:Putty config1.PNG]]
[[File:Putty config2 tunnel.PNG]]

=== Starting a Session and Connecting to Squiggles ===
Ensure you've established an SSH tunnel before proceeding with either the VNC or FastX methods.

==== VNC Method (preferred) ====
* '''Creating & Accessing a VNC Session''':
** VNC sessions initialize automatically upon boot-up.
** If issues occur, manually initiate a session using: <code>vncserver :## -geometry 1900x1200</code>, where <code>##</code> is your specific port number.
** Access the session using the [[https://www.realvnc.com/en/connect/download/viewer/ RealVNC viewer]].
** Input <code>localhost:##</code> in the server address bar, where <code>##</code> corresponds to the last two digits of your port.

[[image:vncviewer.png]]



=== Troubleshooting ===
;'''Identifying Active Users'''
:To compile a list of users with active VNC sessions, which aids in monitoring current access to the VNC service, execute:
:<code>ls -l /tmp/.X11-unix</code>
:This information can be used to oversee session activity and ensure that resources are allocated efficiently.

;'''Terminating a VNC Session'''
:For situations where session termination is necessary, you can directly close a VNC session through the terminal or opt for manual termination if the direct method is insufficient. To directly terminate a session, use:
:<code>vncserver -kill :xx</code>
:Replace <code>:xx</code> with your session number.

;'''Manual Termination of the VNC'''
:For manual termination, proceed to remove the session files with:
:<code>rm -f /tmp/.Xxx-lock</code>
:<code>rm -f /tmp/.X11-unix/Xxx</code>
:Ensure to replace <code>Xxx</code> with the correct session identifier. This allows for removing stuck or unresponsive sessions that cannot be closed normally.

;'''Alternative Solution: when Manual Termination of the VNC does not work'''
:Use the following command, replacing <code><username></code> with the actual username:
:<code>ps -ef | grep <username></code>
:This will list all processes related to the specified user. You can then terminate unwanted sessions by killing the process IDs:
:<code>kill -9 <PID></code>
:Where <code><PID></code> is the process ID obtained from the previous command's output.

:Optional: To check the environment variables active during a VNC session, which can help in troubleshooting further issues, view the VNC environment log:
:<code>cat ~/vnc.log</code>

;'''VNC Black Screen Issue'''
:If you encounter a black screen after logging into VNC, it could be due to the Anaconda Python environment interfering with the session. To resolve this issue, deactivate Anaconda Python using the command:
:<code>conda deactivate</code>
:You can run the command twice. Also, you can run this command to check if conda has been deactivated properly:
:<code>which python</code>
:Alternatively, modify your `~/.bashrc` script, for example, using:
:<code>nano ~/.bashrc</code>
:and comment out the line starting with <code>export PATH=/.../miniconda ..</code>.
:Disconnect and reconnect to squiggles through ssh, run `conda deactivate`, and then start a new VNC session.
:You can also adjust the startup file. Here's an example modification to include in your `.vnc/xstartup` script:
<pre style="margin-left: 20px;">
#!/bin/sh

unset SESSION_MANAGER
unset DBUS_SESSION_BUS_ADDRESS
# exec /etc/X11/xinit/xinitrc

gnome-session
</pre>

Squiggles research computer server

2024-05-17T17:56:25Z

Vahab: /* Troubleshooting */

=== Introduction ===
"Squiggles" is a dedicated research computer server tailored for the analysis and storage of MEG, Neurophysiology, and Epilepsy data. This guide outlines how to connect using either the recommended FastX connection or the traditional VNC method.

=== Access Requirements ===
==== RCC Account ====

* An RCC (Research Computer Server) account is necessary to access "Squiggles".
* Register for an account at [https://docs.rcc.mcw.edu/user-guide/accounts/ MCW-Infoscope's Research Computing Center].
* If prompted, select "others" and then "squiggles" to specify the server you wish to access.
* Account approval generally takes 1-3 days. For any issues, contact Help-RCC at <help-rcc@mcw.edu>.

=== Login to Squiggles ===
'''Choosing a User Port:''' Each user is allocated a specific port number. New users should pick a port number (##) not already in use:

{| class="wikitable"
|-
! scope="col"|User
! scope="col"|Port
|-
|Jeff Stout
|5910, 5911
|-
|Joe Heffernan
|5912
|-
|Manoj Raghavan
|5913, 5998, 5999
|-
|Candida Ustine
|5914
|-
|Chad Carlson
|5915
|-
|Chris Anderson
|5916
|-
|Serena Thompson
|5917
|-
|Patrick Bauer
|5918
|-
|Jeff Binder
|5919
|-
|Leo Fernandino
|5920
|-
|Lisa Conant
|5921
|-
|Aqil Izadysadr
|5922
|-
|Nick Guzowski
|5923
|-
|Zack Harper
|5924
|-
|Bill Gross
|5925
|-
|Michelle Kassel
|5926
|-
|Greg McQuestion
|5927
|-
|Monica Keith
|5928
|-
|Priyanka Shah
|5929
|-
|Vahab Youssof Zadeh
|5931
|-
|Songhee Kim
|5935
|-
|Rupesh Chikara
|5944
|-
|Cameron J Stewart
|5992
|}

===== SSH Tunneling =====
* '''PowerShell Method (Mac/Linux/Windows):''' In a bash shell, terminal, or Windows PowerShell, execute the following to set up an SSH tunnel for the VNC Viewer:
<code>ssh -L 59##:localhost:59## USER@squiggles.rcc.mcw.edu</code>
where USER is your rcc user account and ## is the selected port number

* '''PuTTY (Windows):'''
[https://www.chiark.greenend.org.uk/~sgtatham/putty/ Download PuTTY] for SSH tunneling and refer to the images below for configuration:

PuTTY is an open-source software used for SSH Tunneling (or SSH Port Forwarding).

[[File:Putty config1.PNG]]
[[File:Putty config2 tunnel.PNG]]

=== Starting a Session and Connecting to Squiggles ===
Ensure you've established an SSH tunnel before proceeding with either the VNC or FastX methods.

==== VNC Method (preferred) ====
* '''Creating & Accessing a VNC Session''':
** VNC sessions initialize automatically upon boot-up.
** If issues occur, manually initiate a session using: <code>vncserver :## -geometry 1900x1200</code>, where <code>##</code> is your specific port number.
** Access the session using the [[https://www.realvnc.com/en/connect/download/viewer/ RealVNC viewer]].
** Input <code>localhost:##</code> in the server address bar, where <code>##</code> corresponds to the last two digits of your port.

[[image:vncviewer.png]]



=== Troubleshooting ===
;'''Identifying Active Users'''
:To compile a list of users with active VNC sessions, which aids in monitoring current access to the VNC service, execute:
:<code>ls -l /tmp/.X11-unix</code>
:This information can be used to oversee session activity and ensure that resources are allocated efficiently.

;'''Terminating a VNC Session'''
:For situations where session termination is necessary, you can directly close a VNC session through the terminal or opt for manual termination if the direct method is insufficient. To directly terminate a session, use:
:<code>vncserver -kill :xx</code>
:Replace <code>:xx</code> with your session number.

;'''Manual Termination of the VNC'''
:For manual termination, proceed to remove the session files with:
:<code>rm -f /tmp/.Xxx-lock</code>
:<code>rm -f /tmp/.X11-unix/Xxx</code>
:Ensure to replace <code>Xxx</code> with the correct session identifier. This allows for removing stuck or unresponsive sessions that cannot be closed normally.

;'''Alternative Solution: when Manual Termination of the VNC does not work'''
:Use the following command, replacing <code><username></code> with the actual username:
:<code>ps -ef | grep <username></code>
:This will list all processes related to the specified user. You can then terminate unwanted sessions by killing the process IDs:
:<code>kill -9 <PID></code>
:Where <code><PID></code> is the process ID obtained from the previous command's output.

:Optional: To check the environment variables active during a VNC session, which can help in troubleshooting further issues, view the VNC environment log:
:<code>cat ~/vnc.log</code>

;'''VNC Black Screen Issue'''
:If you encounter a black screen after logging into VNC, it could be due to the Anaconda Python environment interfering with the session. To resolve this issue, deactivate Anaconda Python using the command:
:<code>conda deactivate</code>
:You can run the command twice. Also, you can run this command to check if conda has been deactivated properly:
:<code>which python</code>
:Alternatively, modify your `~/.bashrc` script, for example, using:
:<code>nano ~/.bashrc</code>
:and comment out the line starting with <code>export PATH=/.../miniconda ..</code>.
:Disconnect and reconnect to squiggles through ssh, run `conda deactivate`, and then start a new VNC session.
:You can also adjust the startup file. Here's an example modification to include in your `.vnc/xstartup` script:
<pre style="margin-left: 20px;">
#!/bin/sh

unset SESSION_MANAGER
unset DBUS_SESSION_BUS_ADDRESS
# exec /etc/X11/xinit/xinitrc

gnome-session
</pre>

Squiggles research computer server

2024-05-17T17:52:03Z

Vahab: /* SSH Tunneling */

=== Introduction ===
"Squiggles" is a dedicated research computer server tailored for the analysis and storage of MEG, Neurophysiology, and Epilepsy data. This guide outlines how to connect using either the recommended FastX connection or the traditional VNC method.

=== Access Requirements ===
==== RCC Account ====

* An RCC (Research Computer Server) account is necessary to access "Squiggles".
* Register for an account at [https://docs.rcc.mcw.edu/user-guide/accounts/ MCW-Infoscope's Research Computing Center].
* If prompted, select "others" and then "squiggles" to specify the server you wish to access.
* Account approval generally takes 1-3 days. For any issues, contact Help-RCC at <help-rcc@mcw.edu>.

=== Login to Squiggles ===
'''Choosing a User Port:''' Each user is allocated a specific port number. New users should pick a port number (##) not already in use:

{| class="wikitable"
|-
! scope="col"|User
! scope="col"|Port
|-
|Jeff Stout
|5910, 5911
|-
|Joe Heffernan
|5912
|-
|Manoj Raghavan
|5913, 5998, 5999
|-
|Candida Ustine
|5914
|-
|Chad Carlson
|5915
|-
|Chris Anderson
|5916
|-
|Serena Thompson
|5917
|-
|Patrick Bauer
|5918
|-
|Jeff Binder
|5919
|-
|Leo Fernandino
|5920
|-
|Lisa Conant
|5921
|-
|Aqil Izadysadr
|5922
|-
|Nick Guzowski
|5923
|-
|Zack Harper
|5924
|-
|Bill Gross
|5925
|-
|Michelle Kassel
|5926
|-
|Greg McQuestion
|5927
|-
|Monica Keith
|5928
|-
|Priyanka Shah
|5929
|-
|Vahab Youssof Zadeh
|5931
|-
|Songhee Kim
|5935
|-
|Rupesh Chikara
|5944
|-
|Cameron J Stewart
|5992
|}

===== SSH Tunneling =====
* '''PowerShell Method (Mac/Linux/Windows):''' In a bash shell, terminal, or Windows PowerShell, execute the following to set up an SSH tunnel for the VNC Viewer:
<code>ssh -L 59##:localhost:59## USER@squiggles.rcc.mcw.edu</code>
where USER is your rcc user account and ## is the selected port number

* '''PuTTY (Windows):'''
[https://www.chiark.greenend.org.uk/~sgtatham/putty/ Download PuTTY] for SSH tunneling and refer to the images below for configuration:

PuTTY is an open-source software used for SSH Tunneling (or SSH Port Forwarding).

[[File:Putty config1.PNG]]
[[File:Putty config2 tunnel.PNG]]

=== Starting a Session and Connecting to Squiggles ===
Ensure you've established an SSH tunnel before proceeding with either the VNC or FastX methods.

==== VNC Method (preferred) ====
* '''Creating & Accessing a VNC Session''':
** VNC sessions initialize automatically upon boot-up.
** If issues occur, manually initiate a session using: <code>vncserver :## -geometry 1900x1200</code>, where <code>##</code> is your specific port number.
** Access the session using the [[https://www.realvnc.com/en/connect/download/viewer/ RealVNC viewer]].
** Input <code>localhost:##</code> in the server address bar, where <code>##</code> corresponds to the last two digits of your port.

[[image:vncviewer.png]]



=== Troubleshooting ===

;'''VNC Black Screen Issue'''
:If you encounter a black screen after logging into VNC, it could be due to the Anaconda Python environment interfering with the session. To resolve this issue, deactivate Anaconda Python using the command:
:<code>conda deactivate</code>

:You can run the command twice. Also, you can run this command,

:<code>which python</code>

:to check it conda has been deactivated properly.

:Alternativey, modify your `~/.bashrc` script e.g., using,

:<code>nano ~/.bashrc</code>

:and comment out the line starting with, <code>export PATH=/.../miniconda ..</code>

:disconnect and reconnect to squiggles through ssh, run conda deactivate, and then start a new vnc session

:You can also adjust the startup file. Here's an example modification to include in your `.vnc/xstartup` script:

<pre style="margin-left: 20px;">
#!/bin/sh

unset SESSION_MANAGER
unset DBUS_SESSION_BUS_ADDRESS
# exec /etc/X11/xinit/xinitrc

gnome-session
</pre>

;'''Identifying Active Users'''
:To compile a list of users with active VNC sessions, which aids in monitoring current access to the VNC service, execute:
:<code>ls -l /tmp/.X11-unix</code>
:This information can be used to oversee session activity and ensure that resources are allocated efficiently.

;'''Terminating a VNC Session'''
:For situations where session termination is necessary, you can directly close a VNC session through the terminal or opt for manual termination if the direct method is insufficient. To directly terminate a session, use:
:<code>vncserver -kill :xx</code>
:Replace <code>:xx</code> with your session number.

;'''Manual Termination of the VNC'''
:For manual termination, proceed to remove the session files with:
:<code>rm -f /tmp/.Xxx-lock</code>
:<code>rm -f /tmp/.X11-unix/Xxx</code>
:Ensure to replace <code>Xxx</code> with the correct session identifier. This allows for removing stuck or unresponsive sessions that cannot be closed normally.

;'''Alternative Solution: when Manual Termination of the VNC does not work'''
:Use the following command, replacing <code><username></code> with the actual username:
:<code>ps -ef | grep <username></code>
:This will list all processes related to the specified user. You can then terminate unwanted sessions by killing the process IDs:
:<code>kill -9 <PID></code>
:Where <code><PID></code> is the process ID obtained from the previous command's output.

:Optional: To check the environment variables active during a VNC session, which can help in troubleshooting further issues, view the VNC environment log:
:<code>cat ~/vnc_environment.log</code>

Squiggles research computer server

2024-05-17T17:50:16Z

Vahab: /* Login to Squiggles */

=== Introduction ===
"Squiggles" is a dedicated research computer server tailored for the analysis and storage of MEG, Neurophysiology, and Epilepsy data. This guide outlines how to connect using either the recommended FastX connection or the traditional VNC method.

=== Access Requirements ===
==== RCC Account ====

* An RCC (Research Computer Server) account is necessary to access "Squiggles".
* Register for an account at [https://docs.rcc.mcw.edu/user-guide/accounts/ MCW-Infoscope's Research Computing Center].
* If prompted, select "others" and then "squiggles" to specify the server you wish to access.
* Account approval generally takes 1-3 days. For any issues, contact Help-RCC at <help-rcc@mcw.edu>.

===== SSH Tunneling =====
* '''PowerShell Method (Mac/Linux/Windows):''' In a bash shell, terminal, or Windows PowerShell, execute the following to set up an SSH tunnel for the VNC Viewer:
<code>ssh -L 59##:localhost:59## USER@squiggles.rcc.mcw.edu</code>
where USER is your rcc user account and ## is the selected port number

* '''PuTTY (Windows):'''
[https://www.chiark.greenend.org.uk/~sgtatham/putty/ Download PuTTY] for SSH tunneling and refer to the images below for configuration:

PuTTY is an open-source software used for SSH Tunneling (or SSH Port Forwarding).

[[File:Putty config1.PNG]]
[[File:Putty config2 tunnel.PNG]]

=== Login to Squiggles ===
'''Choosing a User Port:''' Each user is allocated a specific port number. New users should pick a port number (##) not already in use:

{| class="wikitable"
|-
! scope="col"|User
! scope="col"|Port
|-
|Jeff Stout
|5910, 5911
|-
|Joe Heffernan
|5912
|-
|Manoj Raghavan
|5913, 5998, 5999
|-
|Candida Ustine
|5914
|-
|Chad Carlson
|5915
|-
|Chris Anderson
|5916
|-
|Serena Thompson
|5917
|-
|Patrick Bauer
|5918
|-
|Jeff Binder
|5919
|-
|Leo Fernandino
|5920
|-
|Lisa Conant
|5921
|-
|Aqil Izadysadr
|5922
|-
|Nick Guzowski
|5923
|-
|Zack Harper
|5924
|-
|Bill Gross
|5925
|-
|Michelle Kassel
|5926
|-
|Greg McQuestion
|5927
|-
|Monica Keith
|5928
|-
|Priyanka Shah
|5929
|-
|Vahab Youssof Zadeh
|5931
|-
|Songhee Kim
|5935
|-
|Rupesh Chikara
|5944
|-
|Cameron J Stewart
|5992
|}

===== SSH Tunneling =====
* '''PowerShell Method (Mac/Linux/Windows):''' In a bash shell, terminal, or Windows PowerShell, execute the following to set up an SSH tunnel for the VNC Viewer:
<code>ssh -L 59##:localhost:59## USER@squiggles.rcc.mcw.edu</code>
where USER is your rcc user account and ## is the selected port number

* '''PuTTY (Windows):'''
[https://www.chiark.greenend.org.uk/~sgtatham/putty/ Download PuTTY] for SSH tunneling and refer to the images below for configuration:

PuTTY is an open-source software used for SSH Tunneling (or SSH Port Forwarding).

[[File:Putty config1.PNG]]
[[File:Putty config2 tunnel.PNG]]

=== Starting a Session and Connecting to Squiggles ===
Ensure you've established an SSH tunnel before proceeding with either the VNC or FastX methods.

==== VNC Method (preferred) ====
* '''Creating & Accessing a VNC Session''':
** VNC sessions initialize automatically upon boot-up.
** If issues occur, manually initiate a session using: <code>vncserver :## -geometry 1900x1200</code>, where <code>##</code> is your specific port number.
** Access the session using the [[https://www.realvnc.com/en/connect/download/viewer/ RealVNC viewer]].
** Input <code>localhost:##</code> in the server address bar, where <code>##</code> corresponds to the last two digits of your port.

[[image:vncviewer.png]]



=== Troubleshooting ===

;'''VNC Black Screen Issue'''
:If you encounter a black screen after logging into VNC, it could be due to the Anaconda Python environment interfering with the session. To resolve this issue, deactivate Anaconda Python using the command:
:<code>conda deactivate</code>

:You can run the command twice. Also, you can run this command,

:<code>which python</code>

:to check it conda has been deactivated properly.

:Alternativey, modify your `~/.bashrc` script e.g., using,

:<code>nano ~/.bashrc</code>

:and comment out the line starting with, <code>export PATH=/.../miniconda ..</code>

:disconnect and reconnect to squiggles through ssh, run conda deactivate, and then start a new vnc session

:You can also adjust the startup file. Here's an example modification to include in your `.vnc/xstartup` script:

<pre style="margin-left: 20px;">
#!/bin/sh

unset SESSION_MANAGER
unset DBUS_SESSION_BUS_ADDRESS
# exec /etc/X11/xinit/xinitrc

gnome-session
</pre>

;'''Identifying Active Users'''
:To compile a list of users with active VNC sessions, which aids in monitoring current access to the VNC service, execute:
:<code>ls -l /tmp/.X11-unix</code>
:This information can be used to oversee session activity and ensure that resources are allocated efficiently.

;'''Terminating a VNC Session'''
:For situations where session termination is necessary, you can directly close a VNC session through the terminal or opt for manual termination if the direct method is insufficient. To directly terminate a session, use:
:<code>vncserver -kill :xx</code>
:Replace <code>:xx</code> with your session number.

;'''Manual Termination of the VNC'''
:For manual termination, proceed to remove the session files with:
:<code>rm -f /tmp/.Xxx-lock</code>
:<code>rm -f /tmp/.X11-unix/Xxx</code>
:Ensure to replace <code>Xxx</code> with the correct session identifier. This allows for removing stuck or unresponsive sessions that cannot be closed normally.

;'''Alternative Solution: when Manual Termination of the VNC does not work'''
:Use the following command, replacing <code><username></code> with the actual username:
:<code>ps -ef | grep <username></code>
:This will list all processes related to the specified user. You can then terminate unwanted sessions by killing the process IDs:
:<code>kill -9 <PID></code>
:Where <code><PID></code> is the process ID obtained from the previous command's output.

:Optional: To check the environment variables active during a VNC session, which can help in troubleshooting further issues, view the VNC environment log:
:<code>cat ~/vnc_environment.log</code>

Squiggles research computer server

2024-05-17T17:45:10Z

Vahab: /* Login to Squiggles */

=== Introduction ===
"Squiggles" is a dedicated research computer server tailored for the analysis and storage of MEG, Neurophysiology, and Epilepsy data. This guide outlines how to connect using either the recommended FastX connection or the traditional VNC method.

=== Access Requirements ===
==== RCC Account ====

* An RCC (Research Computer Server) account is necessary to access "Squiggles".
* Register for an account at [https://docs.rcc.mcw.edu/user-guide/accounts/ MCW-Infoscope's Research Computing Center].
* If prompted, select "others" and then "squiggles" to specify the server you wish to access.
* Account approval generally takes 1-3 days. For any issues, contact Help-RCC at <help-rcc@mcw.edu>.

=== Login to Squiggles ===
'''Choosing a User Port:''' Each user is allocated a specific port number. New users should pick a port number (##) not already in use:

{| class="wikitable"
|-
! scope="col"|User
! scope="col"|Port
|-
|Jeff Stout
|5910,5911
|-
|Joe Heffernan
|5912
|-
|Candida Ustine
|5914
|-
|Manoj Raghavan
|5913
|-
|Chad Carlson
|5915
|-
|Chris Anderson
|5916
|-
|Serena Thompson
|5917
|-
|Patrick Bauer
|5918
|-
|Jeff Binder
|5919
|-
|Leo Fernandino
|5920
|-
|Lisa Conant
|5921
|-
|Aqil Izadysadr
|5922
|-
|Nick Guzowski
|5923
|-
|Zack Harper
|5924
|-
|Bill Gross
|5925
|-
|Michelle Kassel
|5926
|-
|Greg McQuestion
|5927
|-
|Monica Keith
|5928
|-
|Priyanka Shah
|5929
|-
|Vahab Youssof Zadeh
|5931
|-
|Songhee Kim
|5935
|-
|Cameron J Stewart
|5992
|-
|Rupesh Chikara
|5944
|}
===== SSH Tunneling =====
* '''PowerShell Method (Mac/Linux/Windows):''' In a bash shell, terminal, or Windows PowerShell, execute the following to set up an SSH tunnel for the VNC Viewer:
<code>ssh -L 59##:localhost:59## USER@squiggles.rcc.mcw.edu</code>
where USER is your rcc user account and ## is the selected port number

* '''PuTTY (Windows):'''
[https://www.chiark.greenend.org.uk/~sgtatham/putty/ Download PuTTY] for SSH tunneling and refer to the images below for configuration:

PuTTY is an open-source software used for SSH Tunneling (or SSH Port Forwarding).

[[File:Putty config1.PNG]]
[[File:Putty config2 tunnel.PNG]]

=== Starting a Session and Connecting to Squiggles ===
Ensure you've established an SSH tunnel before proceeding with either the VNC or FastX methods.

==== VNC Method (preferred) ====
* '''Creating & Accessing a VNC Session''':
** VNC sessions initialize automatically upon boot-up.
** If issues occur, manually initiate a session using: <code>vncserver :## -geometry 1900x1200</code>, where <code>##</code> is your specific port number.
** Access the session using the [[https://www.realvnc.com/en/connect/download/viewer/ RealVNC viewer]].
** Input <code>localhost:##</code> in the server address bar, where <code>##</code> corresponds to the last two digits of your port.

[[image:vncviewer.png]]



=== Troubleshooting ===

;'''VNC Black Screen Issue'''
:If you encounter a black screen after logging into VNC, it could be due to the Anaconda Python environment interfering with the session. To resolve this issue, deactivate Anaconda Python using the command:
:<code>conda deactivate</code>

:You can run the command twice. Also, you can run this command,

:<code>which python</code>

:to check it conda has been deactivated properly.

:Alternativey, modify your `~/.bashrc` script e.g., using,

:<code>nano ~/.bashrc</code>

:and comment out the line starting with, <code>export PATH=/.../miniconda ..</code>

:disconnect and reconnect to squiggles through ssh, run conda deactivate, and then start a new vnc session

:You can also adjust the startup file. Here's an example modification to include in your `.vnc/xstartup` script:

<pre style="margin-left: 20px;">
#!/bin/sh

unset SESSION_MANAGER
unset DBUS_SESSION_BUS_ADDRESS
# exec /etc/X11/xinit/xinitrc

gnome-session
</pre>

;'''Identifying Active Users'''
:To compile a list of users with active VNC sessions, which aids in monitoring current access to the VNC service, execute:
:<code>ls -l /tmp/.X11-unix</code>
:This information can be used to oversee session activity and ensure that resources are allocated efficiently.

;'''Terminating a VNC Session'''
:For situations where session termination is necessary, you can directly close a VNC session through the terminal or opt for manual termination if the direct method is insufficient. To directly terminate a session, use:
:<code>vncserver -kill :xx</code>
:Replace <code>:xx</code> with your session number.

;'''Manual Termination of the VNC'''
:For manual termination, proceed to remove the session files with:
:<code>rm -f /tmp/.Xxx-lock</code>
:<code>rm -f /tmp/.X11-unix/Xxx</code>
:Ensure to replace <code>Xxx</code> with the correct session identifier. This allows for removing stuck or unresponsive sessions that cannot be closed normally.

;'''Alternative Solution: when Manual Termination of the VNC does not work'''
:Use the following command, replacing <code><username></code> with the actual username:
:<code>ps -ef | grep <username></code>
:This will list all processes related to the specified user. You can then terminate unwanted sessions by killing the process IDs:
:<code>kill -9 <PID></code>
:Where <code><PID></code> is the process ID obtained from the previous command's output.

:Optional: To check the environment variables active during a VNC session, which can help in troubleshooting further issues, view the VNC environment log:
:<code>cat ~/vnc_environment.log</code>

Squiggles research computer server

2024-05-17T17:44:49Z

Vahab: /* Login to Squiggles */

=== Introduction ===
"Squiggles" is a dedicated research computer server tailored for the analysis and storage of MEG, Neurophysiology, and Epilepsy data. This guide outlines how to connect using either the recommended FastX connection or the traditional VNC method.

=== Access Requirements ===
==== RCC Account ====

* An RCC (Research Computer Server) account is necessary to access "Squiggles".
* Register for an account at [https://docs.rcc.mcw.edu/user-guide/accounts/ MCW-Infoscope's Research Computing Center].
* If prompted, select "others" and then "squiggles" to specify the server you wish to access.
* Account approval generally takes 1-3 days. For any issues, contact Help-RCC at <help-rcc@mcw.edu>.

=== Login to Squiggles ===
'''Choosing a User Port:''' Each user is allocated a specific port number. New users should pick a port number (##) not already in use:

{| class="wikitable"
|-
! scope="col"|User
! scope="col"|Port
|-
|Jeff Stout
|5910,5911
|-
|Joe Heffernan
|5912
|-
|Candida Ustine
|5914
|-
|Manoj Raghavan
|5913
|-
|Chad Carlson
|5915
|-
|Chris Anderson
|5916
|-
|Serena Thompson
|5917
|-
|Patrick Bauer
|5918
|-
|Jeff Binder
|5919
|-
|Leo Fernandino
|5920
|-
|Lisa Conant
|5921
|-
|Aqil Izadysadr
|5922
|-
|Nick Guzowski
|5923
|-
|Zack Harper
|5924
|-
|Bill Gross
|5925
|-
|Michelle Kassel
|5926
|-
|Greg McQuestion
|5927
|-
|Monica Keith
|5928
|-
|Priyanka Shah
|5929
|-
|Vahab Youssofzadeh
|5931
|-
|Songhee Kim
|5935
|-
|Cameron J Stewart
|5992
|-
|Rupesh Chikara
|5944
|}
===== SSH Tunneling =====
* '''PowerShell Method (Mac/Linux/Windows):''' In a bash shell, terminal, or Windows PowerShell, execute the following to set up an SSH tunnel for the VNC Viewer:
<code>ssh -L 59##:localhost:59## USER@squiggles.rcc.mcw.edu</code>
where USER is your rcc user account and ## is the selected port number

* '''PuTTY (Windows):'''
[https://www.chiark.greenend.org.uk/~sgtatham/putty/ Download PuTTY] for SSH tunneling and refer to the images below for configuration:

PuTTY is an open-source software used for SSH Tunneling (or SSH Port Forwarding).

[[File:Putty config1.PNG]]
[[File:Putty config2 tunnel.PNG]]

=== Starting a Session and Connecting to Squiggles ===
Ensure you've established an SSH tunnel before proceeding with either the VNC or FastX methods.

==== VNC Method (preferred) ====
* '''Creating & Accessing a VNC Session''':
** VNC sessions initialize automatically upon boot-up.
** If issues occur, manually initiate a session using: <code>vncserver :## -geometry 1900x1200</code>, where <code>##</code> is your specific port number.
** Access the session using the [[https://www.realvnc.com/en/connect/download/viewer/ RealVNC viewer]].
** Input <code>localhost:##</code> in the server address bar, where <code>##</code> corresponds to the last two digits of your port.

[[image:vncviewer.png]]



=== Troubleshooting ===

;'''VNC Black Screen Issue'''
:If you encounter a black screen after logging into VNC, it could be due to the Anaconda Python environment interfering with the session. To resolve this issue, deactivate Anaconda Python using the command:
:<code>conda deactivate</code>

:You can run the command twice. Also, you can run this command,

:<code>which python</code>

:to check it conda has been deactivated properly.

:Alternativey, modify your `~/.bashrc` script e.g., using,

:<code>nano ~/.bashrc</code>

:and comment out the line starting with, <code>export PATH=/.../miniconda ..</code>

:disconnect and reconnect to squiggles through ssh, run conda deactivate, and then start a new vnc session

:You can also adjust the startup file. Here's an example modification to include in your `.vnc/xstartup` script:

<pre style="margin-left: 20px;">
#!/bin/sh

unset SESSION_MANAGER
unset DBUS_SESSION_BUS_ADDRESS
# exec /etc/X11/xinit/xinitrc

gnome-session
</pre>

;'''Identifying Active Users'''
:To compile a list of users with active VNC sessions, which aids in monitoring current access to the VNC service, execute:
:<code>ls -l /tmp/.X11-unix</code>
:This information can be used to oversee session activity and ensure that resources are allocated efficiently.

;'''Terminating a VNC Session'''
:For situations where session termination is necessary, you can directly close a VNC session through the terminal or opt for manual termination if the direct method is insufficient. To directly terminate a session, use:
:<code>vncserver -kill :xx</code>
:Replace <code>:xx</code> with your session number.

;'''Manual Termination of the VNC'''
:For manual termination, proceed to remove the session files with:
:<code>rm -f /tmp/.Xxx-lock</code>
:<code>rm -f /tmp/.X11-unix/Xxx</code>
:Ensure to replace <code>Xxx</code> with the correct session identifier. This allows for removing stuck or unresponsive sessions that cannot be closed normally.

;'''Alternative Solution: when Manual Termination of the VNC does not work'''
:Use the following command, replacing <code><username></code> with the actual username:
:<code>ps -ef | grep <username></code>
:This will list all processes related to the specified user. You can then terminate unwanted sessions by killing the process IDs:
:<code>kill -9 <PID></code>
:Where <code><PID></code> is the process ID obtained from the previous command's output.

:Optional: To check the environment variables active during a VNC session, which can help in troubleshooting further issues, view the VNC environment log:
:<code>cat ~/vnc_environment.log</code>

Squiggles research computer server

2024-05-17T17:44:19Z

Vahab: /* Login to Squiggles */

=== Introduction ===
"Squiggles" is a dedicated research computer server tailored for the analysis and storage of MEG, Neurophysiology, and Epilepsy data. This guide outlines how to connect using either the recommended FastX connection or the traditional VNC method.

=== Access Requirements ===
==== RCC Account ====

* An RCC (Research Computer Server) account is necessary to access "Squiggles".
* Register for an account at [https://docs.rcc.mcw.edu/user-guide/accounts/ MCW-Infoscope's Research Computing Center].
* If prompted, select "others" and then "squiggles" to specify the server you wish to access.
* Account approval generally takes 1-3 days. For any issues, contact Help-RCC at <help-rcc@mcw.edu>.

=== Login to Squiggles ===
'''Choosing a User Port:''' Each user is allocated a specific port number. New users should pick a port number (##) not already in use:

{| class="wikitable"
|-
! scope="col"|User
! scope="col"|Port
|-
|Jeff Stout
|5910,5911
|-
|Joe Heffernan
|5912
|-
|Candida Ustine
|5914
|-
|Manoj Raghavan
|5913
|-
|Chad Carlson
|5915
|-
|Chris Anderson
|5916
|-
|Serena Thompson
|5917
|-
|Patrick Bauer
|5918
|-
|Jeff Binder
|5919
|-
|Leo Fernandino
|5920
|-
|Lisa Conant
|5921
|-
|Aqil Izadysadr
|5922
|-
|Nick Guzowski
|5923
|-
|Zack Harper
|5924
|-
|Bill Gross
|5925
|-
|Michelle Kassel
|5926
|-
|Greg McQuestion
|5927
|-
|Monica Keith
|5928
|-
|Priyanka Shah
|5929
|-
|Vahab Youssofzadeh
|5931
|-
|Songhee Kim
|5935
|-
|Cameron J Stewart
|5992
|Rupesh Chikara
|5944
|}
===== SSH Tunneling =====
* '''PowerShell Method (Mac/Linux/Windows):''' In a bash shell, terminal, or Windows PowerShell, execute the following to set up an SSH tunnel for the VNC Viewer:
<code>ssh -L 59##:localhost:59## USER@squiggles.rcc.mcw.edu</code>
where USER is your rcc user account and ## is the selected port number

* '''PuTTY (Windows):'''
[https://www.chiark.greenend.org.uk/~sgtatham/putty/ Download PuTTY] for SSH tunneling and refer to the images below for configuration:

PuTTY is an open-source software used for SSH Tunneling (or SSH Port Forwarding).

[[File:Putty config1.PNG]]
[[File:Putty config2 tunnel.PNG]]

=== Starting a Session and Connecting to Squiggles ===
Ensure you've established an SSH tunnel before proceeding with either the VNC or FastX methods.

==== VNC Method (preferred) ====
* '''Creating & Accessing a VNC Session''':
** VNC sessions initialize automatically upon boot-up.
** If issues occur, manually initiate a session using: <code>vncserver :## -geometry 1900x1200</code>, where <code>##</code> is your specific port number.
** Access the session using the [[https://www.realvnc.com/en/connect/download/viewer/ RealVNC viewer]].
** Input <code>localhost:##</code> in the server address bar, where <code>##</code> corresponds to the last two digits of your port.

[[image:vncviewer.png]]



=== Troubleshooting ===

;'''VNC Black Screen Issue'''
:If you encounter a black screen after logging into VNC, it could be due to the Anaconda Python environment interfering with the session. To resolve this issue, deactivate Anaconda Python using the command:
:<code>conda deactivate</code>

:You can run the command twice. Also, you can run this command,

:<code>which python</code>

:to check it conda has been deactivated properly.

:Alternativey, modify your `~/.bashrc` script e.g., using,

:<code>nano ~/.bashrc</code>

:and comment out the line starting with, <code>export PATH=/.../miniconda ..</code>

:disconnect and reconnect to squiggles through ssh, run conda deactivate, and then start a new vnc session

:You can also adjust the startup file. Here's an example modification to include in your `.vnc/xstartup` script:

<pre style="margin-left: 20px;">
#!/bin/sh

unset SESSION_MANAGER
unset DBUS_SESSION_BUS_ADDRESS
# exec /etc/X11/xinit/xinitrc

gnome-session
</pre>

;'''Identifying Active Users'''
:To compile a list of users with active VNC sessions, which aids in monitoring current access to the VNC service, execute:
:<code>ls -l /tmp/.X11-unix</code>
:This information can be used to oversee session activity and ensure that resources are allocated efficiently.

;'''Terminating a VNC Session'''
:For situations where session termination is necessary, you can directly close a VNC session through the terminal or opt for manual termination if the direct method is insufficient. To directly terminate a session, use:
:<code>vncserver -kill :xx</code>
:Replace <code>:xx</code> with your session number.

;'''Manual Termination of the VNC'''
:For manual termination, proceed to remove the session files with:
:<code>rm -f /tmp/.Xxx-lock</code>
:<code>rm -f /tmp/.X11-unix/Xxx</code>
:Ensure to replace <code>Xxx</code> with the correct session identifier. This allows for removing stuck or unresponsive sessions that cannot be closed normally.

;'''Alternative Solution: when Manual Termination of the VNC does not work'''
:Use the following command, replacing <code><username></code> with the actual username:
:<code>ps -ef | grep <username></code>
:This will list all processes related to the specified user. You can then terminate unwanted sessions by killing the process IDs:
:<code>kill -9 <PID></code>
:Where <code><PID></code> is the process ID obtained from the previous command's output.

:Optional: To check the environment variables active during a VNC session, which can help in troubleshooting further issues, view the VNC environment log:
:<code>cat ~/vnc_environment.log</code>

Squiggles research computer server

2024-05-17T17:43:48Z

Vahab: /* Troubleshooting */

=== Introduction ===
"Squiggles" is a dedicated research computer server tailored for the analysis and storage of MEG, Neurophysiology, and Epilepsy data. This guide outlines how to connect using either the recommended FastX connection or the traditional VNC method.

=== Access Requirements ===
==== RCC Account ====

* An RCC (Research Computer Server) account is necessary to access "Squiggles".
* Register for an account at [https://docs.rcc.mcw.edu/user-guide/accounts/ MCW-Infoscope's Research Computing Center].
* If prompted, select "others" and then "squiggles" to specify the server you wish to access.
* Account approval generally takes 1-3 days. For any issues, contact Help-RCC at <help-rcc@mcw.edu>.

=== Login to Squiggles ===
'''Choosing a User Port:''' Each user is allocated a specific port number. New users should pick a port number (##) not already in use:

{| class="wikitable"
|-
! scope="col"|User
! scope="col"|Port
|-
|Jeff Stout
|5910,5911
|-
|Joe Heffernan
|5912
|-
|Candida Ustine
|5914
|-
|Manoj Raghavan
|5913
|-
|Chad Carlson
|5915
|-
|Chris Anderson
|5916
|-
|Serena Thompson
|5917
|-
|Patrick Bauer
|5918
|-
|Jeff Binder
|5919
|-
|Leo Fernandino
|5920
|-
|Lisa Conant
|5921
|-
|Aqil Izadysadr
|5922
|-
|Nick Guzowski
|5923
|-
|Zack Harper
|5924
|-
|Bill Gross
|5925
|-
|Michelle Kassel
|5926
|-
|Greg McQuestion
|5927
|-
|Monica Keith
|5928
|-
|Priyanka Shah
|5929
|-
|Vahab Youssofzadeh
|5931
|-
|Songhee Kim
|5935
|-
|Cameron J Stewart
|5992
|}
===== SSH Tunneling =====
* '''PowerShell Method (Mac/Linux/Windows):''' In a bash shell, terminal, or Windows PowerShell, execute the following to set up an SSH tunnel for the VNC Viewer:
<code>ssh -L 59##:localhost:59## USER@squiggles.rcc.mcw.edu</code>
where USER is your rcc user account and ## is the selected port number

* '''PuTTY (Windows):'''
[https://www.chiark.greenend.org.uk/~sgtatham/putty/ Download PuTTY] for SSH tunneling and refer to the images below for configuration:

PuTTY is an open-source software used for SSH Tunneling (or SSH Port Forwarding).

[[File:Putty config1.PNG]]
[[File:Putty config2 tunnel.PNG]]

=== Starting a Session and Connecting to Squiggles ===
Ensure you've established an SSH tunnel before proceeding with either the VNC or FastX methods.

==== VNC Method (preferred) ====
* '''Creating & Accessing a VNC Session''':
** VNC sessions initialize automatically upon boot-up.
** If issues occur, manually initiate a session using: <code>vncserver :## -geometry 1900x1200</code>, where <code>##</code> is your specific port number.
** Access the session using the [[https://www.realvnc.com/en/connect/download/viewer/ RealVNC viewer]].
** Input <code>localhost:##</code> in the server address bar, where <code>##</code> corresponds to the last two digits of your port.

[[image:vncviewer.png]]



=== Troubleshooting ===

;'''VNC Black Screen Issue'''
:If you encounter a black screen after logging into VNC, it could be due to the Anaconda Python environment interfering with the session. To resolve this issue, deactivate Anaconda Python using the command:
:<code>conda deactivate</code>

:You can run the command twice. Also, you can run this command,

:<code>which python</code>

:to check it conda has been deactivated properly.

:Alternativey, modify your `~/.bashrc` script e.g., using,

:<code>nano ~/.bashrc</code>

:and comment out the line starting with, <code>export PATH=/.../miniconda ..</code>

:disconnect and reconnect to squiggles through ssh, run conda deactivate, and then start a new vnc session

:You can also adjust the startup file. Here's an example modification to include in your `.vnc/xstartup` script:

<pre style="margin-left: 20px;">
#!/bin/sh

unset SESSION_MANAGER
unset DBUS_SESSION_BUS_ADDRESS
# exec /etc/X11/xinit/xinitrc

gnome-session
</pre>

;'''Identifying Active Users'''
:To compile a list of users with active VNC sessions, which aids in monitoring current access to the VNC service, execute:
:<code>ls -l /tmp/.X11-unix</code>
:This information can be used to oversee session activity and ensure that resources are allocated efficiently.

;'''Terminating a VNC Session'''
:For situations where session termination is necessary, you can directly close a VNC session through the terminal or opt for manual termination if the direct method is insufficient. To directly terminate a session, use:
:<code>vncserver -kill :xx</code>
:Replace <code>:xx</code> with your session number.

;'''Manual Termination of the VNC'''
:For manual termination, proceed to remove the session files with:
:<code>rm -f /tmp/.Xxx-lock</code>
:<code>rm -f /tmp/.X11-unix/Xxx</code>
:Ensure to replace <code>Xxx</code> with the correct session identifier. This allows for removing stuck or unresponsive sessions that cannot be closed normally.

;'''Alternative Solution: when Manual Termination of the VNC does not work'''
:Use the following command, replacing <code><username></code> with the actual username:
:<code>ps -ef | grep <username></code>
:This will list all processes related to the specified user. You can then terminate unwanted sessions by killing the process IDs:
:<code>kill -9 <PID></code>
:Where <code><PID></code> is the process ID obtained from the previous command's output.

:Optional: To check the environment variables active during a VNC session, which can help in troubleshooting further issues, view the VNC environment log:
:<code>cat ~/vnc_environment.log</code>

Squiggles research computer server

2024-05-17T17:34:09Z

Vahab: /* Troubleshooting */

=== Introduction ===
"Squiggles" is a dedicated research computer server tailored for the analysis and storage of MEG, Neurophysiology, and Epilepsy data. This guide outlines how to connect using either the recommended FastX connection or the traditional VNC method.

=== Access Requirements ===
==== RCC Account ====

* An RCC (Research Computer Server) account is necessary to access "Squiggles".
* Register for an account at [https://docs.rcc.mcw.edu/user-guide/accounts/ MCW-Infoscope's Research Computing Center].
* If prompted, select "others" and then "squiggles" to specify the server you wish to access.
* Account approval generally takes 1-3 days. For any issues, contact Help-RCC at <help-rcc@mcw.edu>.

=== Login to Squiggles ===
'''Choosing a User Port:''' Each user is allocated a specific port number. New users should pick a port number (##) not already in use:

{| class="wikitable"
|-
! scope="col"|User
! scope="col"|Port
|-
|Jeff Stout
|5910,5911
|-
|Joe Heffernan
|5912
|-
|Candida Ustine
|5914
|-
|Manoj Raghavan
|5913
|-
|Chad Carlson
|5915
|-
|Chris Anderson
|5916
|-
|Serena Thompson
|5917
|-
|Patrick Bauer
|5918
|-
|Jeff Binder
|5919
|-
|Leo Fernandino
|5920
|-
|Lisa Conant
|5921
|-
|Aqil Izadysadr
|5922
|-
|Nick Guzowski
|5923
|-
|Zack Harper
|5924
|-
|Bill Gross
|5925
|-
|Michelle Kassel
|5926
|-
|Greg McQuestion
|5927
|-
|Monica Keith
|5928
|-
|Priyanka Shah
|5929
|-
|Vahab Youssofzadeh
|5931
|-
|Songhee Kim
|5935
|-
|Cameron J Stewart
|5992
|}
===== SSH Tunneling =====
* '''PowerShell Method (Mac/Linux/Windows):''' In a bash shell, terminal, or Windows PowerShell, execute the following to set up an SSH tunnel for the VNC Viewer:
<code>ssh -L 59##:localhost:59## USER@squiggles.rcc.mcw.edu</code>
where USER is your rcc user account and ## is the selected port number

* '''PuTTY (Windows):'''
[https://www.chiark.greenend.org.uk/~sgtatham/putty/ Download PuTTY] for SSH tunneling and refer to the images below for configuration:

PuTTY is an open-source software used for SSH Tunneling (or SSH Port Forwarding).

[[File:Putty config1.PNG]]
[[File:Putty config2 tunnel.PNG]]

=== Starting a Session and Connecting to Squiggles ===
Ensure you've established an SSH tunnel before proceeding with either the VNC or FastX methods.

==== VNC Method (preferred) ====
* '''Creating & Accessing a VNC Session''':
** VNC sessions initialize automatically upon boot-up.
** If issues occur, manually initiate a session using: <code>vncserver :## -geometry 1900x1200</code>, where <code>##</code> is your specific port number.
** Access the session using the [[https://www.realvnc.com/en/connect/download/viewer/ RealVNC viewer]].
** Input <code>localhost:##</code> in the server address bar, where <code>##</code> corresponds to the last two digits of your port.

[[image:vncviewer.png]]



=== Troubleshooting ===

;'''VNC Black Screen Issue'''
:If you encounter a black screen after logging into VNC, it could be due to the Anaconda Python environment interfering with the session. To resolve this issue, deactivate Anaconda Python using the command:
:<code>conda deactivate</code>
:Alternativey, modify your `.vnc/xstartup` script e.g., using,

:<code>nano ~/.vnc/xstartupc</code>

:to adjust the `PATH` and deactivate Conda before starting the desktop environment. Here's an example modification to include in your `.vnc/xstartup` script:

<pre style="margin-left: 20px;">
#!/bin/sh

unset SESSION_MANAGER
unset DBUS_SESSION_BUS_ADDRESS
# exec /etc/X11/xinit/xinitrc

gnome-session
</pre>

;'''Identifying Active Users'''
:To compile a list of users with active VNC sessions, which aids in monitoring current access to the VNC service, execute:
:<code>ls -l /tmp/.X11-unix</code>
:This information can be used to oversee session activity and ensure that resources are allocated efficiently.

;'''Terminating a VNC Session'''
:For situations where session termination is necessary, you can directly close a VNC session through the terminal or opt for manual termination if the direct method is insufficient. To directly terminate a session, use:
:<code>vncserver -kill :xx</code>
:Replace <code>:xx</code> with your session number.

;'''Manual Termination of the VNC'''
:For manual termination, proceed to remove the session files with:
:<code>rm -f /tmp/.Xxx-lock</code>
:<code>rm -f /tmp/.X11-unix/Xxx</code>
:Ensure to replace <code>Xxx</code> with the correct session identifier. This allows for removing stuck or unresponsive sessions that cannot be closed normally.

;'''Alternative Solution: when Manual Termination of the VNC does not work'''
:Use the following command, replacing <code><username></code> with the actual username:
:<code>ps -ef | grep <username></code>
:This will list all processes related to the specified user. You can then terminate unwanted sessions by killing the process IDs:
:<code>kill -9 <PID></code>
:Where <code><PID></code> is the process ID obtained from the previous command's output.

:Optional: To check the environment variables active during a VNC session, which can help in troubleshooting further issues, view the VNC environment log:
:<code>cat ~/vnc_environment.log</code>

Squiggles research computer server

2024-05-15T15:24:04Z

Vahab: /* Troubleshooting */

=== Introduction ===
"Squiggles" is a dedicated research computer server tailored for the analysis and storage of MEG, Neurophysiology, and Epilepsy data. This guide outlines how to connect using either the recommended FastX connection or the traditional VNC method.

=== Access Requirements ===
==== RCC Account ====

* An RCC (Research Computer Server) account is necessary to access "Squiggles".
* Register for an account at [https://docs.rcc.mcw.edu/user-guide/accounts/ MCW-Infoscope's Research Computing Center].
* If prompted, select "others" and then "squiggles" to specify the server you wish to access.
* Account approval generally takes 1-3 days. For any issues, contact Help-RCC at <help-rcc@mcw.edu>.

=== Login to Squiggles ===
'''Choosing a User Port:''' Each user is allocated a specific port number. New users should pick a port number (##) not already in use:

{| class="wikitable"
|-
! scope="col"|User
! scope="col"|Port
|-
|Jeff Stout
|5910,5911
|-
|Joe Heffernan
|5912
|-
|Candida Ustine
|5914
|-
|Manoj Raghavan
|5913
|-
|Chad Carlson
|5915
|-
|Chris Anderson
|5916
|-
|Serena Thompson
|5917
|-
|Patrick Bauer
|5918
|-
|Jeff Binder
|5919
|-
|Leo Fernandino
|5920
|-
|Lisa Conant
|5921
|-
|Aqil Izadysadr
|5922
|-
|Nick Guzowski
|5923
|-
|Zack Harper
|5924
|-
|Bill Gross
|5925
|-
|Michelle Kassel
|5926
|-
|Greg McQuestion
|5927
|-
|Monica Keith
|5928
|-
|Priyanka Shah
|5929
|-
|Vahab Youssofzadeh
|5931
|-
|Songhee Kim
|5935
|-
|Cameron J Stewart
|5992
|}
===== SSH Tunneling =====
* '''PowerShell Method (Mac/Linux/Windows):''' In a bash shell, terminal, or Windows PowerShell, execute the following to set up an SSH tunnel for the VNC Viewer:
<code>ssh -L 59##:localhost:59## USER@squiggles.rcc.mcw.edu</code>
where USER is your rcc user account and ## is the selected port number

* '''PuTTY (Windows):'''
[https://www.chiark.greenend.org.uk/~sgtatham/putty/ Download PuTTY] for SSH tunneling and refer to the images below for configuration:

PuTTY is an open-source software used for SSH Tunneling (or SSH Port Forwarding).

[[File:Putty config1.PNG]]
[[File:Putty config2 tunnel.PNG]]

=== Starting a Session and Connecting to Squiggles ===
Ensure you've established an SSH tunnel before proceeding with either the VNC or FastX methods.

==== VNC Method (preferred) ====
* '''Creating & Accessing a VNC Session''':
** VNC sessions initialize automatically upon boot-up.
** If issues occur, manually initiate a session using: <code>vncserver :## -geometry 1900x1200</code>, where <code>##</code> is your specific port number.
** Access the session using the [[https://www.realvnc.com/en/connect/download/viewer/ RealVNC viewer]].
** Input <code>localhost:##</code> in the server address bar, where <code>##</code> corresponds to the last two digits of your port.

[[image:vncviewer.png]]



=== Troubleshooting ===

;'''VNC Black Screen Issue'''
:If you encounter a black screen after logging into VNC, it could be due to the Anaconda Python environment interfering with the session. To resolve this issue, deactivate Anaconda Python using the command:
:<code>conda deactivate</code>
:Alternativey, modify your `.vnc/xstartup` script e.g., using,

:<code>nano ~/.vnc/xstartupc</code>

:to adjust the `PATH` and deactivate Conda before starting the desktop environment. Here's an example modification to include in your `.vnc/xstartup` script:

<pre style="margin-left: 20px;">
#!/bin/sh
# Log environment variables to help with debugging
printenv > ~/vnc_environment.log

unset SESSION_MANAGER
unset DBUS_SESSION_BUS_ADDRESS
# exec /etc/X11/xinit/xinitrc

# Adjust PATH and deactivate Conda
export PATH=/usr/local/bin:/usr/bin:/bin:$PATH
conda deactivate

gnome-session
</pre>

;'''Identifying Active Users'''
:To compile a list of users with active VNC sessions, which aids in monitoring current access to the VNC service, execute:
:<code>ls -l /tmp/.X11-unix</code>
:This information can be used to oversee session activity and ensure that resources are allocated efficiently.

;'''Terminating a VNC Session'''
:For situations where session termination is necessary, you can directly close a VNC session through the terminal or opt for manual termination if the direct method is insufficient. To directly terminate a session, use:
:<code>vncserver -kill :xx</code>
:Replace <code>:xx</code> with your session number.

;'''Manual Termination of the VNC'''
:For manual termination, proceed to remove the session files with:
:<code>rm -f /tmp/.Xxx-lock</code>
:<code>rm -f /tmp/.X11-unix/Xxx</code>
:Ensure to replace <code>Xxx</code> with the correct session identifier. This allows for removing stuck or unresponsive sessions that cannot be closed normally.

;'''Alternative Solution: when Manual Termination of the VNC does not work'''
:Use the following command, replacing <code><username></code> with the actual username:
:<code>ps -ef | grep <username></code>
:This will list all processes related to the specified user. You can then terminate unwanted sessions by killing the process IDs:
:<code>kill -9 <PID></code>
:Where <code><PID></code> is the process ID obtained from the previous command's output.

:Optional: To check the environment variables active during a VNC session, which can help in troubleshooting further issues, view the VNC environment log:
:<code>cat ~/vnc_environment.log</code>

Squiggles research computer server

2024-05-15T15:20:32Z

Vahab: /* Troubleshooting */

=== Introduction ===
"Squiggles" is a dedicated research computer server tailored for the analysis and storage of MEG, Neurophysiology, and Epilepsy data. This guide outlines how to connect using either the recommended FastX connection or the traditional VNC method.

=== Access Requirements ===
==== RCC Account ====

* An RCC (Research Computer Server) account is necessary to access "Squiggles".
* Register for an account at [https://docs.rcc.mcw.edu/user-guide/accounts/ MCW-Infoscope's Research Computing Center].
* If prompted, select "others" and then "squiggles" to specify the server you wish to access.
* Account approval generally takes 1-3 days. For any issues, contact Help-RCC at <help-rcc@mcw.edu>.

=== Login to Squiggles ===
'''Choosing a User Port:''' Each user is allocated a specific port number. New users should pick a port number (##) not already in use:

{| class="wikitable"
|-
! scope="col"|User
! scope="col"|Port
|-
|Jeff Stout
|5910,5911
|-
|Joe Heffernan
|5912
|-
|Candida Ustine
|5914
|-
|Manoj Raghavan
|5913
|-
|Chad Carlson
|5915
|-
|Chris Anderson
|5916
|-
|Serena Thompson
|5917
|-
|Patrick Bauer
|5918
|-
|Jeff Binder
|5919
|-
|Leo Fernandino
|5920
|-
|Lisa Conant
|5921
|-
|Aqil Izadysadr
|5922
|-
|Nick Guzowski
|5923
|-
|Zack Harper
|5924
|-
|Bill Gross
|5925
|-
|Michelle Kassel
|5926
|-
|Greg McQuestion
|5927
|-
|Monica Keith
|5928
|-
|Priyanka Shah
|5929
|-
|Vahab Youssofzadeh
|5931
|-
|Songhee Kim
|5935
|-
|Cameron J Stewart
|5992
|}
===== SSH Tunneling =====
* '''PowerShell Method (Mac/Linux/Windows):''' In a bash shell, terminal, or Windows PowerShell, execute the following to set up an SSH tunnel for the VNC Viewer:
<code>ssh -L 59##:localhost:59## USER@squiggles.rcc.mcw.edu</code>
where USER is your rcc user account and ## is the selected port number

* '''PuTTY (Windows):'''
[https://www.chiark.greenend.org.uk/~sgtatham/putty/ Download PuTTY] for SSH tunneling and refer to the images below for configuration:

PuTTY is an open-source software used for SSH Tunneling (or SSH Port Forwarding).

[[File:Putty config1.PNG]]
[[File:Putty config2 tunnel.PNG]]

=== Starting a Session and Connecting to Squiggles ===
Ensure you've established an SSH tunnel before proceeding with either the VNC or FastX methods.

==== VNC Method (preferred) ====
* '''Creating & Accessing a VNC Session''':
** VNC sessions initialize automatically upon boot-up.
** If issues occur, manually initiate a session using: <code>vncserver :## -geometry 1900x1200</code>, where <code>##</code> is your specific port number.
** Access the session using the [[https://www.realvnc.com/en/connect/download/viewer/ RealVNC viewer]].
** Input <code>localhost:##</code> in the server address bar, where <code>##</code> corresponds to the last two digits of your port.

[[image:vncviewer.png]]



=== Troubleshooting ===

;'''VNC Black Screen Issue'''
:If you encounter a black screen after logging into VNC, it could be due to the Anaconda Python environment interfering with the session. To resolve this issue, deactivate Anaconda Python using the command:
:<code>conda deactivate</code>
:Alternativey, modify your `.vnc/xstartup` script e.g., using,

:<code>nano ~/.vnc/xstartupc</code>

:to adjust the `PATH` and deactivate Conda before starting the desktop environment. Here's an example modification to include in your `.vnc/xstartup` script:

<pre style="margin-left: 20px;">
#!/bin/sh
# Log environment variables to help with debugging
printenv > ~/vnc_environment.log

unset SESSION_MANAGER
unset DBUS_SESSION_BUS_ADDRESS
# exec /etc/X11/xinit/xinitrc

# Adjust PATH and deactivate Conda
export PATH=/usr/local/bin:/usr/bin:/bin:$PATH
conda deactivate

gnome-session
</pre>

;'''Identifying Active Users'''
:To compile a list of users with active VNC sessions, which aids in monitoring current access to the VNC service, execute:
:<code>ls -l /tmp/.X11-unix</code>
:This information can be used to oversee session activity and ensure that resources are allocated efficiently.

;'''Terminating a VNC Session'''
:For situations where session termination is necessary, you can directly close a VNC session through the terminal or opt for manual termination if the direct method is insufficient. To directly terminate a session, use:
:<code>vncserver -kill :xx</code>
:Replace <code>:xx</code> with your session number.

;'''Manual Termination of the VNC'''
:For manual termination, proceed to remove the session files with:
:<code>rm -f /tmp/.Xxx-lock</code>
:<code>rm -f /tmp/.X11-unix/Xxx</code>
:Ensure to replace <code>Xxx</code> with the correct session identifier. This allows for the removal of stuck or unresponsive sessions that cannot be closed normally.

;'''Alternative Solution: Identifying Active Sessions and Terminating a VNC Session'''
:Identifying sessions created by a specific user can be a strategic approach to session management, offering an alternative to manual session termination. This method is particularly useful for identifying and removing only unnecessary or problematic sessions. Use the following command, replacing <code><username></code> with the actual username:
:<code>ps -ef | grep <username></code>
:This will list all processes related to the specified user. You can then terminate unwanted sessions by killing the process IDs:
:<code>kill -9 <PID></code>
:Where <code><PID></code> is the process ID obtained from the output of the previous command.

:To check the environment variables active during a VNC session, which can help in troubleshooting further issues, view the VNC environment log:
:<code>cat ~/vnc_environment.log</code>

Squiggles research computer server

2024-05-15T15:18:09Z

Vahab: /* Troubleshooting */

=== Introduction ===
"Squiggles" is a dedicated research computer server tailored for the analysis and storage of MEG, Neurophysiology, and Epilepsy data. This guide outlines how to connect using either the recommended FastX connection or the traditional VNC method.

=== Access Requirements ===
==== RCC Account ====

* An RCC (Research Computer Server) account is necessary to access "Squiggles".
* Register for an account at [https://docs.rcc.mcw.edu/user-guide/accounts/ MCW-Infoscope's Research Computing Center].
* If prompted, select "others" and then "squiggles" to specify the server you wish to access.
* Account approval generally takes 1-3 days. For any issues, contact Help-RCC at <help-rcc@mcw.edu>.

=== Login to Squiggles ===
'''Choosing a User Port:''' Each user is allocated a specific port number. New users should pick a port number (##) not already in use:

{| class="wikitable"
|-
! scope="col"|User
! scope="col"|Port
|-
|Jeff Stout
|5910,5911
|-
|Joe Heffernan
|5912
|-
|Candida Ustine
|5914
|-
|Manoj Raghavan
|5913
|-
|Chad Carlson
|5915
|-
|Chris Anderson
|5916
|-
|Serena Thompson
|5917
|-
|Patrick Bauer
|5918
|-
|Jeff Binder
|5919
|-
|Leo Fernandino
|5920
|-
|Lisa Conant
|5921
|-
|Aqil Izadysadr
|5922
|-
|Nick Guzowski
|5923
|-
|Zack Harper
|5924
|-
|Bill Gross
|5925
|-
|Michelle Kassel
|5926
|-
|Greg McQuestion
|5927
|-
|Monica Keith
|5928
|-
|Priyanka Shah
|5929
|-
|Vahab Youssofzadeh
|5931
|-
|Songhee Kim
|5935
|-
|Cameron J Stewart
|5992
|}
===== SSH Tunneling =====
* '''PowerShell Method (Mac/Linux/Windows):''' In a bash shell, terminal, or Windows PowerShell, execute the following to set up an SSH tunnel for the VNC Viewer:
<code>ssh -L 59##:localhost:59## USER@squiggles.rcc.mcw.edu</code>
where USER is your rcc user account and ## is the selected port number

* '''PuTTY (Windows):'''
[https://www.chiark.greenend.org.uk/~sgtatham/putty/ Download PuTTY] for SSH tunneling and refer to the images below for configuration:

PuTTY is an open-source software used for SSH Tunneling (or SSH Port Forwarding).

[[File:Putty config1.PNG]]
[[File:Putty config2 tunnel.PNG]]

=== Starting a Session and Connecting to Squiggles ===
Ensure you've established an SSH tunnel before proceeding with either the VNC or FastX methods.

==== VNC Method (preferred) ====
* '''Creating & Accessing a VNC Session''':
** VNC sessions initialize automatically upon boot-up.
** If issues occur, manually initiate a session using: <code>vncserver :## -geometry 1900x1200</code>, where <code>##</code> is your specific port number.
** Access the session using the [[https://www.realvnc.com/en/connect/download/viewer/ RealVNC viewer]].
** Input <code>localhost:##</code> in the server address bar, where <code>##</code> corresponds to the last two digits of your port.

[[image:vncviewer.png]]



=== Troubleshooting ===

;'''VNC Black Screen Issue'''
:If you encounter a black screen after logging into VNC, it could be due to the Anaconda Python environment interfering with the session. To resolve this issue, deactivate Anaconda Python using the command:
:<code>conda deactivate</code>
:Alternativey, modify your `.vnc/xstartup` script e.g., using,

:<code>nano ~/.vnc/xstartupc</code>

:to adjust the `PATH` and deactivate Conda before starting the desktop environment. Here's an example modification to include in your `.vnc/xstartup` script:

<pre style="margin-left: 20px;">
#!/bin/sh
# Log environment variables to help with debugging
printenv > ~/vnc_environment.log

unset SESSION_MANAGER
unset DBUS_SESSION_BUS_ADDRESS
# exec /etc/X11/xinit/xinitrc

# Adjust PATH and deactivate Conda
export PATH=/usr/local/bin:/usr/bin:/bin:$PATH
conda deactivate

gnome-session
</pre>

;'''Identifying Active Users'''
:To compile a list of users with active VNC sessions, which aids in monitoring current access to the VNC service, execute:
:<code>ls -l /tmp/.X11-unix</code>
:This information can be used to oversee session activity and ensure that resources are allocated efficiently.

;'''Terminating a VNC Session'''
:For situations where session termination is necessary, you can directly close a VNC session through the terminal or opt for manual termination if the direct method is insufficient. To directly terminate a session, use:
:<code>vncserver -kill :xx</code>
:Replace <code>:xx</code> with your session number.

:For manual termination, proceed to remove the session files with:
:<code>rm -f /tmp/.Xxx-lock</code>
:<code>rm -f /tmp/.X11-unix/Xxx</code>
:Ensure to replace <code>Xxx</code> with the correct session identifier. This allows for the removal of stuck or unresponsive sessions that cannot be closed normally.

;'''Alternative Solution: Identifying Active Sessions and Terminating a VNC Session'''
:Identifying sessions created by a specific user can be a strategic approach to session management, offering an alternative to manual session termination. This method is particularly useful for identifying and removing only unnecessary or problematic sessions. Use the following command, replacing <code><username></code> with the actual username:
:<code>ps -ef | grep <username></code>
:This will list all processes related to the specified user. You can then terminate unwanted sessions by killing the process IDs:
:<code>kill -9 <PID></code>
:Where <code><PID></code> is the process ID obtained from the output of the previous command.

:To check the environment variables active during a VNC session, which can help in troubleshooting further issues, view the VNC environment log:
:<code>cat ~/vnc_environment.log</code>

Squiggles research computer server

2024-05-15T15:16:46Z

Vahab: /* Troubleshooting */

=== Introduction ===
"Squiggles" is a dedicated research computer server tailored for the analysis and storage of MEG, Neurophysiology, and Epilepsy data. This guide outlines how to connect using either the recommended FastX connection or the traditional VNC method.

=== Access Requirements ===
==== RCC Account ====

* An RCC (Research Computer Server) account is necessary to access "Squiggles".
* Register for an account at [https://docs.rcc.mcw.edu/user-guide/accounts/ MCW-Infoscope's Research Computing Center].
* If prompted, select "others" and then "squiggles" to specify the server you wish to access.
* Account approval generally takes 1-3 days. For any issues, contact Help-RCC at <help-rcc@mcw.edu>.

=== Login to Squiggles ===
'''Choosing a User Port:''' Each user is allocated a specific port number. New users should pick a port number (##) not already in use:

{| class="wikitable"
|-
! scope="col"|User
! scope="col"|Port
|-
|Jeff Stout
|5910,5911
|-
|Joe Heffernan
|5912
|-
|Candida Ustine
|5914
|-
|Manoj Raghavan
|5913
|-
|Chad Carlson
|5915
|-
|Chris Anderson
|5916
|-
|Serena Thompson
|5917
|-
|Patrick Bauer
|5918
|-
|Jeff Binder
|5919
|-
|Leo Fernandino
|5920
|-
|Lisa Conant
|5921
|-
|Aqil Izadysadr
|5922
|-
|Nick Guzowski
|5923
|-
|Zack Harper
|5924
|-
|Bill Gross
|5925
|-
|Michelle Kassel
|5926
|-
|Greg McQuestion
|5927
|-
|Monica Keith
|5928
|-
|Priyanka Shah
|5929
|-
|Vahab Youssofzadeh
|5931
|-
|Songhee Kim
|5935
|-
|Cameron J Stewart
|5992
|}
===== SSH Tunneling =====
* '''PowerShell Method (Mac/Linux/Windows):''' In a bash shell, terminal, or Windows PowerShell, execute the following to set up an SSH tunnel for the VNC Viewer:
<code>ssh -L 59##:localhost:59## USER@squiggles.rcc.mcw.edu</code>
where USER is your rcc user account and ## is the selected port number

* '''PuTTY (Windows):'''
[https://www.chiark.greenend.org.uk/~sgtatham/putty/ Download PuTTY] for SSH tunneling and refer to the images below for configuration:

PuTTY is an open-source software used for SSH Tunneling (or SSH Port Forwarding).

[[File:Putty config1.PNG]]
[[File:Putty config2 tunnel.PNG]]

=== Starting a Session and Connecting to Squiggles ===
Ensure you've established an SSH tunnel before proceeding with either the VNC or FastX methods.

==== VNC Method (preferred) ====
* '''Creating & Accessing a VNC Session''':
** VNC sessions initialize automatically upon boot-up.
** If issues occur, manually initiate a session using: <code>vncserver :## -geometry 1900x1200</code>, where <code>##</code> is your specific port number.
** Access the session using the [[https://www.realvnc.com/en/connect/download/viewer/ RealVNC viewer]].
** Input <code>localhost:##</code> in the server address bar, where <code>##</code> corresponds to the last two digits of your port.

[[image:vncviewer.png]]



=== Troubleshooting ===

;'''VNC Black Screen Issue'''
:If you encounter a black screen after logging into VNC, it could be due to the Anaconda Python environment interfering with the session. To resolve this issue, deactivate Anaconda Python using the command:
:<code>conda deactivate</code>
:Alternativey, modify your `.vnc/xstartup` script e.g., using,

:<code>nano ~/.vnc/xstartupc</code>

:to adjust the `PATH` and deactivate Conda before starting the desktop environment. Here's an example modification to include in your `.vnc/xstartup` script:

<pre style="margin-left: 20px;">
#!/bin/sh
# Log environment variables to help with debugging
printenv > ~/vnc_environment.log

unset SESSION_MANAGER
unset DBUS_SESSION_BUS_ADDRESS
# exec /etc/X11/xinit/xinitrc

# Adjust PATH and deactivate Conda
export PATH=/usr/local/bin:/usr/bin:/bin:$PATH
conda deactivate

gnome-session
</pre>

;'''Identifying Active Users'''
:To compile a list of users with active VNC sessions, which aids in monitoring current access to the VNC service, execute:
:<code>ls -l /tmp/.X11-unix</code>
:This information can be used to oversee session activity and ensure that resources are allocated efficiently.

;'''Terminating a VNC Session'''
:For situations where session termination is necessary, you can directly close a VNC session through the terminal or opt for manual termination if the direct method is insufficient. To directly terminate a session, use:
:<code>vncserver -kill :xx</code>
:Replace <code>:xx</code> with your session number.

:For manual termination, proceed to remove the session files with:
:<code>rm -f /tmp/.Xxx-lock</code>
:<code>rm -f /tmp/.X11-unix/Xxx</code>
:Ensure to replace <code>Xxx</code> with the correct session identifier. This allows for the removal of stuck or unresponsive sessions that cannot be closed normally.

;'''Alternative Solution: Identifying Active Sessions'''
:Identifying sessions created by a specific user can be a strategic approach to session management, offering an alternative to manual session termination. This method is particularly useful for identifying and removing only unnecessary or problematic sessions. Use the following command, replacing <code><username></code> with the actual username:
:<code>ps -ef | grep <username></code>
:This will list all processes related to the specified user. You can then terminate unwanted sessions by killing the process IDs:
:<code>kill -9 <PID></code>
:Where <code><PID></code> is the process ID obtained from the output of the previous command.

:To check the environment variables active during a VNC session, which can help in troubleshooting further issues, view the VNC environment log:
:<code>cat ~/vnc_environment.log</code>

Squiggles research computer server

2024-05-15T01:11:54Z

Vahab: /* Troubleshooting */

=== Introduction ===
"Squiggles" is a dedicated research computer server tailored for the analysis and storage of MEG, Neurophysiology, and Epilepsy data. This guide outlines how to connect using either the recommended FastX connection or the traditional VNC method.

=== Access Requirements ===
==== RCC Account ====

* An RCC (Research Computer Server) account is necessary to access "Squiggles".
* Register for an account at [https://docs.rcc.mcw.edu/user-guide/accounts/ MCW-Infoscope's Research Computing Center].
* If prompted, select "others" and then "squiggles" to specify the server you wish to access.
* Account approval generally takes 1-3 days. For any issues, contact Help-RCC at <help-rcc@mcw.edu>.

=== Login to Squiggles ===
'''Choosing a User Port:''' Each user is allocated a specific port number. New users should pick a port number (##) not already in use:

{| class="wikitable"
|-
! scope="col"|User
! scope="col"|Port
|-
|Jeff Stout
|5910,5911
|-
|Joe Heffernan
|5912
|-
|Candida Ustine
|5914
|-
|Manoj Raghavan
|5913
|-
|Chad Carlson
|5915
|-
|Chris Anderson
|5916
|-
|Serena Thompson
|5917
|-
|Patrick Bauer
|5918
|-
|Jeff Binder
|5919
|-
|Leo Fernandino
|5920
|-
|Lisa Conant
|5921
|-
|Aqil Izadysadr
|5922
|-
|Nick Guzowski
|5923
|-
|Zack Harper
|5924
|-
|Bill Gross
|5925
|-
|Michelle Kassel
|5926
|-
|Greg McQuestion
|5927
|-
|Monica Keith
|5928
|-
|Priyanka Shah
|5929
|-
|Vahab Youssofzadeh
|5931
|-
|Songhee Kim
|5935
|-
|Cameron J Stewart
|5992
|}
===== SSH Tunneling =====
* '''PowerShell Method (Mac/Linux/Windows):''' In a bash shell, terminal, or Windows PowerShell, execute the following to set up an SSH tunnel for the VNC Viewer:
<code>ssh -L 59##:localhost:59## USER@squiggles.rcc.mcw.edu</code>
where USER is your rcc user account and ## is the selected port number

* '''PuTTY (Windows):'''
[https://www.chiark.greenend.org.uk/~sgtatham/putty/ Download PuTTY] for SSH tunneling and refer to the images below for configuration:

PuTTY is an open-source software used for SSH Tunneling (or SSH Port Forwarding).

[[File:Putty config1.PNG]]
[[File:Putty config2 tunnel.PNG]]

=== Starting a Session and Connecting to Squiggles ===
Ensure you've established an SSH tunnel before proceeding with either the VNC or FastX methods.

==== VNC Method (preferred) ====
* '''Creating & Accessing a VNC Session''':
** VNC sessions initialize automatically upon boot-up.
** If issues occur, manually initiate a session using: <code>vncserver :## -geometry 1900x1200</code>, where <code>##</code> is your specific port number.
** Access the session using the [[https://www.realvnc.com/en/connect/download/viewer/ RealVNC viewer]].
** Input <code>localhost:##</code> in the server address bar, where <code>##</code> corresponds to the last two digits of your port.

[[image:vncviewer.png]]



=== Troubleshooting ===

;'''VNC Black Screen Issue'''
:If you encounter a black screen after logging into VNC, it could be due to the Anaconda Python environment interfering with the session. To resolve this issue, deactivate Anaconda Python using the command:
:<code>conda deactivate</code>
:Alternativey, modify your `.vnc/xstartup` script to adjust the `PATH` and deactivate Conda before starting the desktop environment. Here's an example modification to include in your `.vnc/xstartup` script:

<pre style="margin-left: 20px;">
#!/bin/sh
# Log environment variables to help with debugging
printenv > ~/vnc_environment.log

unset SESSION_MANAGER
unset DBUS_SESSION_BUS_ADDRESS
# exec /etc/X11/xinit/xinitrc

# Adjust PATH and deactivate Conda
export PATH=/usr/local/bin:/usr/bin:/bin:$PATH
conda deactivate

gnome-session
</pre>

;'''Identifying Active Users'''
:To compile a list of users with active VNC sessions, which aids in monitoring current access to the VNC service, execute:
:<code>ls -l /tmp/.X11-unix</code>
:This information can be used to oversee session activity and ensure that resources are allocated efficiently.

;'''Terminating a VNC Session'''
:For situations where session termination is necessary, you can directly close a VNC session through the terminal or opt for manual termination if the direct method is insufficient. To directly terminate a session, use:
:<code>vncserver -kill :xx</code>
:Replace <code>:xx</code> with your session number.

:For manual termination, proceed to remove the session files with:
:<code>rm -f /tmp/.Xxx-lock</code>
:<code>rm -f /tmp/.X11-unix/Xxx</code>
:Ensure to replace <code>Xxx</code> with the correct session identifier. This allows for the removal of stuck or unresponsive sessions that cannot be closed normally.

;'''Alternative Solution: Identifying Active Sessions'''
:Identifying sessions created by a specific user can be a strategic approach to session management, offering an alternative to manual session termination. This method is particularly useful for identifying and removing only unnecessary or problematic sessions. Use the following command, replacing <code><username></code> with the actual username:
:<code>ps -ef | grep <username></code>
:This will list all processes related to the specified user. You can then terminate unwanted sessions by killing the process IDs:
:<code>kill -9 <PID></code>
:Where <code><PID></code> is the process ID obtained from the output of the previous command.

:To check the environment variables active during a VNC session, which can help in troubleshooting further issues, view the VNC environment log:
:<code>cat ~/vnc_environment.log</code>

Squiggles research computer server

2024-05-15T01:05:31Z

Vahab:

=== Introduction ===
"Squiggles" is a dedicated research computer server tailored for the analysis and storage of MEG, Neurophysiology, and Epilepsy data. This guide outlines how to connect using either the recommended FastX connection or the traditional VNC method.

=== Access Requirements ===
==== RCC Account ====

* An RCC (Research Computer Server) account is necessary to access "Squiggles".
* Register for an account at [https://docs.rcc.mcw.edu/user-guide/accounts/ MCW-Infoscope's Research Computing Center].
* If prompted, select "others" and then "squiggles" to specify the server you wish to access.
* Account approval generally takes 1-3 days. For any issues, contact Help-RCC at <help-rcc@mcw.edu>.

=== Login to Squiggles ===
'''Choosing a User Port:''' Each user is allocated a specific port number. New users should pick a port number (##) not already in use:

{| class="wikitable"
|-
! scope="col"|User
! scope="col"|Port
|-
|Jeff Stout
|5910,5911
|-
|Joe Heffernan
|5912
|-
|Candida Ustine
|5914
|-
|Manoj Raghavan
|5913
|-
|Chad Carlson
|5915
|-
|Chris Anderson
|5916
|-
|Serena Thompson
|5917
|-
|Patrick Bauer
|5918
|-
|Jeff Binder
|5919
|-
|Leo Fernandino
|5920
|-
|Lisa Conant
|5921
|-
|Aqil Izadysadr
|5922
|-
|Nick Guzowski
|5923
|-
|Zack Harper
|5924
|-
|Bill Gross
|5925
|-
|Michelle Kassel
|5926
|-
|Greg McQuestion
|5927
|-
|Monica Keith
|5928
|-
|Priyanka Shah
|5929
|-
|Vahab Youssofzadeh
|5931
|-
|Songhee Kim
|5935
|-
|Cameron J Stewart
|5992
|}
===== SSH Tunneling =====
* '''PowerShell Method (Mac/Linux/Windows):''' In a bash shell, terminal, or Windows PowerShell, execute the following to set up an SSH tunnel for the VNC Viewer:
<code>ssh -L 59##:localhost:59## USER@squiggles.rcc.mcw.edu</code>
where USER is your rcc user account and ## is the selected port number

* '''PuTTY (Windows):'''
[https://www.chiark.greenend.org.uk/~sgtatham/putty/ Download PuTTY] for SSH tunneling and refer to the images below for configuration:

PuTTY is an open-source software used for SSH Tunneling (or SSH Port Forwarding).

[[File:Putty config1.PNG]]
[[File:Putty config2 tunnel.PNG]]

=== Starting a Session and Connecting to Squiggles ===
Ensure you've established an SSH tunnel before proceeding with either the VNC or FastX methods.

==== VNC Method (preferred) ====
* '''Creating & Accessing a VNC Session''':
** VNC sessions initialize automatically upon boot-up.
** If issues occur, manually initiate a session using: <code>vncserver :## -geometry 1900x1200</code>, where <code>##</code> is your specific port number.
** Access the session using the [[https://www.realvnc.com/en/connect/download/viewer/ RealVNC viewer]].
** Input <code>localhost:##</code> in the server address bar, where <code>##</code> corresponds to the last two digits of your port.

[[image:vncviewer.png]]



=== Troubleshooting ===

;'''VNC Black Screen Issue'''
:If you encounter a black screen after logging into VNC, it could be due to the Anaconda Python environment interfering with the session. To resolve this issue, deactivate Anaconda Python using the command:
:<code>conda deactivate</code>
:Alternativey, modify your `.vnc/xstartup` script to adjust the `PATH` and deactivate Conda before starting the desktop environment. Here's an example modification to include in your `.vnc/xstartup` script:

<pre>
#!/bin/sh
# Log environment variables to help with debugging
printenv > ~/vnc_environment.log

unset SESSION_MANAGER
unset DBUS_SESSION_BUS_ADDRESS
# exec /etc/X11/xinit/xinitrc

# Adjust PATH and deactivate Conda
export PATH=/usr/local/bin:/usr/bin:/bin:$PATH
conda deactivate

gnome-session
</pre>

;'''Identifying Active Users'''
:To compile a list of users with active VNC sessions, which aids in monitoring current access to the VNC service, execute:
:<code>ls -l /tmp/.X11-unix</code>
:This information can be used to oversee session activity and ensure that resources are allocated efficiently.

;'''Terminating a VNC Session'''
:For situations where session termination is necessary, you can directly close a VNC session through the terminal or opt for manual termination if the direct method is insufficient. To directly terminate a session, use:
:<code>vncserver -kill :xx</code>
:Replace <code>:xx</code> with your session number.

:For manual termination, proceed to remove the session files with:
:<code>rm -f /tmp/.Xxx-lock</code>
:<code>rm -f /tmp/.X11-unix/Xxx</code>
:Ensure to replace <code>Xxx</code> with the correct session identifier. This allows for the removal of stuck or unresponsive sessions that cannot be closed normally.

;'''Alternative Solution: Identifying Active Sessions'''
:Identifying sessions created by a specific user can be a strategic approach to session management, offering an alternative to manual session termination. This method is particularly useful for identifying and removing only unnecessary or problematic sessions. Use the following command, replacing <code><username></code> with the actual username:
:<code>ps -ef | grep <username></code>
:This will list all processes related to the specified user. You can then terminate unwanted sessions by killing the process IDs:
:<code>kill -9 <PID></code>
:Where <code><PID></code> is the process ID obtained from the output of the previous command.

:To check the environment variables active during a VNC session, which can help in troubleshooting further issues, view the VNC environment log:
:<code>cat ~/vnc_environment.log</code>

Squiggles research computer server

2024-05-15T01:03:17Z

Vahab: /* Troubleshooting */

=== Introduction ===
"Squiggles" is a dedicated research computer server tailored for the analysis and storage of MEG, Neurophysiology, and Epilepsy data. This guide outlines how to connect using either the recommended FastX connection or the traditional VNC method.

=== Access Requirements ===
==== RCC Account ====

* An RCC (Research Computer Server) account is necessary to access "Squiggles".
* Register for an account at [https://docs.rcc.mcw.edu/user-guide/accounts/ MCW-Infoscope's Research Computing Center].
* If prompted, select "others" and then "squiggles" to specify the server you wish to access.
* Account approval generally takes 1-3 days. For any issues, contact Help-RCC at <help-rcc@mcw.edu>.

=== Login to Squiggles ===
'''Choosing a User Port:''' Each user is allocated a specific port number. New users should pick a port number (##) not already in use:

{| class="wikitable"
|-
! scope="col"|User
! scope="col"|Port
|-
|Jeff Stout
|5910,5911
|-
|Joe Heffernan
|5912
|-
|Candida Ustine
|5914
|-
|Manoj Raghavan
|5913
|-
|Chad Carlson
|5915
|-
|Chris Anderson
|5916
|-
|Serena Thompson
|5917
|-
|Patrick Bauer
|5918
|-
|Jeff Binder
|5919
|-
|Leo Fernandino
|5920
|-
|Lisa Conant
|5921
|-
|Aqil Izadysadr
|5922
|-
|Nick Guzowski
|5923
|-
|Zack Harper
|5924
|-
|Bill Gross
|5925
|-
|Michelle Kassel
|5926
|-
|Greg McQuestion
|5927
|-
|Monica Keith
|5928
|-
|Priyanka Shah
|5929
|-
|Vahab Youssofzadeh
|5931
|-
|Songhee Kim
|5935
|-
|Cameron J Stewart
|5992
|}
===== SSH Tunneling =====
* '''PowerShell Method (Mac/Linux/Windows):''' In a bash shell, terminal, or Windows PowerShell, execute the following to set up an SSH tunnel for the VNC Viewer:
<code>ssh -L 59##:localhost:59## USER@squiggles.rcc.mcw.edu</code>
where USER is your rcc user account and ## is the selected port number

* '''PuTTY (Windows):'''
[https://www.chiark.greenend.org.uk/~sgtatham/putty/ Download PuTTY] for SSH tunneling and refer to the images below for configuration:

PuTTY is an open-source software used for SSH Tunneling (or SSH Port Forwarding).

[[File:Putty config1.PNG]]
[[File:Putty config2 tunnel.PNG]]

=== Starting a Session and Connecting to Squiggles ===
Ensure you've established an SSH tunnel before proceeding with either the VNC or FastX methods.

==== VNC Method (preferred) ====
* '''Creating & Accessing a VNC Session''':
** VNC sessions initialize automatically upon boot-up.
** If issues occur, manually initiate a session using: <code>vncserver :## -geometry 1900x1200</code>, where <code>##</code> is your specific port number.
** Access the session using the [[https://www.realvnc.com/en/connect/download/viewer/ RealVNC viewer]].
** Input <code>localhost:##</code> in the server address bar, where <code>##</code> corresponds to the last two digits of your port.

[[image:vncviewer.png]]

==== FastX Method (alternative) ====
FastX offers a potentially smoother experience compared to VNC, especially with multiple concurrent users.
* Download the [https://www.starnet.com/fastx/current-client FastX client] and:
** Start FastX.
** Click '+' to establish a new connection.
** Provide the Connection Name, host (squiggles.rcc.mcw.edu), and your RCC username.
** Start a session by clicking '+' and using the command <code>/etc/X11/xinit/xinitrc</code>.

[[File: FastX_config.png]]

=== Troubleshooting ===

;'''VNC Black Screen Issue'''
:If you encounter a black screen after logging into VNC, it could be due to the Anaconda Python environment interfering with the session. To resolve this issue, deactivate Anaconda Python using the command:
:<code>conda deactivate</code>
:Alternativey, modify your `.vnc/xstartup` script to adjust the `PATH` and deactivate Conda before starting the desktop environment. Here's an example modification to include in your `.vnc/xstartup` script:

<pre>
#!/bin/sh
# Log environment variables to help with debugging
printenv > ~/vnc_environment.log

unset SESSION_MANAGER
unset DBUS_SESSION_BUS_ADDRESS
# exec /etc/X11/xinit/xinitrc

# Adjust PATH and deactivate Conda
export PATH=/usr/local/bin:/usr/bin:/bin:$PATH
conda deactivate

gnome-session
</pre>

;'''Identifying Active Users'''
:To compile a list of users with active VNC sessions, which aids in monitoring current access to the VNC service, execute:
:<code>ls -l /tmp/.X11-unix</code>
:This information can be used to oversee session activity and ensure that resources are allocated efficiently.

;'''Terminating a VNC Session'''
:For situations where session termination is necessary, you can directly close a VNC session through the terminal or opt for manual termination if the direct method is insufficient. To directly terminate a session, use:
:<code>vncserver -kill :xx</code>
:Replace <code>:xx</code> with your session number.

:For manual termination, proceed to remove the session files with:
:<code>rm -f /tmp/.Xxx-lock</code>
:<code>rm -f /tmp/.X11-unix/Xxx</code>
:Ensure to replace <code>Xxx</code> with the correct session identifier. This allows for the removal of stuck or unresponsive sessions that cannot be closed normally.

;'''Alternative Solution: Identifying Active Sessions'''
:Identifying sessions created by a specific user can be a strategic approach to session management, offering an alternative to manual session termination. This method is particularly useful for identifying and removing only unnecessary or problematic sessions. Use the following command, replacing <code><username></code> with the actual username:
:<code>ps -ef | grep <username></code>
:This will list all processes related to the specified user. You can then terminate unwanted sessions by killing the process IDs:
:<code>kill -9 <PID></code>
:Where <code><PID></code> is the process ID obtained from the output of the previous command.

:To check the environment variables active during a VNC session, which can help in troubleshooting further issues, view the VNC environment log:
:<code>cat ~/vnc_environment.log</code>

Squiggles research computer server

2024-05-15T00:25:51Z

Vahab: /* Troubleshooting */

=== Introduction ===
"Squiggles" is a dedicated research computer server tailored for the analysis and storage of MEG, Neurophysiology, and Epilepsy data. This guide outlines how to connect using either the recommended FastX connection or the traditional VNC method.

=== Access Requirements ===
==== RCC Account ====

* An RCC (Research Computer Server) account is necessary to access "Squiggles".
* Register for an account at [https://docs.rcc.mcw.edu/user-guide/accounts/ MCW-Infoscope's Research Computing Center].
* If prompted, select "others" and then "squiggles" to specify the server you wish to access.
* Account approval generally takes 1-3 days. For any issues, contact Help-RCC at <help-rcc@mcw.edu>.

=== Login to Squiggles ===
'''Choosing a User Port:''' Each user is allocated a specific port number. New users should pick a port number (##) not already in use:

{| class="wikitable"
|-
! scope="col"|User
! scope="col"|Port
|-
|Jeff Stout
|5910,5911
|-
|Joe Heffernan
|5912
|-
|Candida Ustine
|5914
|-
|Manoj Raghavan
|5913
|-
|Chad Carlson
|5915
|-
|Chris Anderson
|5916
|-
|Serena Thompson
|5917
|-
|Patrick Bauer
|5918
|-
|Jeff Binder
|5919
|-
|Leo Fernandino
|5920
|-
|Lisa Conant
|5921
|-
|Aqil Izadysadr
|5922
|-
|Nick Guzowski
|5923
|-
|Zack Harper
|5924
|-
|Bill Gross
|5925
|-
|Michelle Kassel
|5926
|-
|Greg McQuestion
|5927
|-
|Monica Keith
|5928
|-
|Priyanka Shah
|5929
|-
|Vahab Youssofzadeh
|5931
|-
|Songhee Kim
|5935
|-
|Cameron J Stewart
|5992
|}
===== SSH Tunneling =====
* '''PowerShell Method (Mac/Linux/Windows):''' In a bash shell, terminal, or Windows PowerShell, execute the following to set up an SSH tunnel for the VNC Viewer:
<code>ssh -L 59##:localhost:59## USER@squiggles.rcc.mcw.edu</code>
where USER is your rcc user account and ## is the selected port number

* '''PuTTY (Windows):'''
[https://www.chiark.greenend.org.uk/~sgtatham/putty/ Download PuTTY] for SSH tunneling and refer to the images below for configuration:

PuTTY is an open-source software used for SSH Tunneling (or SSH Port Forwarding).

[[File:Putty config1.PNG]]
[[File:Putty config2 tunnel.PNG]]

=== Starting a Session and Connecting to Squiggles ===
Ensure you've established an SSH tunnel before proceeding with either the VNC or FastX methods.

==== VNC Method (preferred) ====
* '''Creating & Accessing a VNC Session''':
** VNC sessions initialize automatically upon boot-up.
** If issues occur, manually initiate a session using: <code>vncserver :## -geometry 1900x1200</code>, where <code>##</code> is your specific port number.
** Access the session using the [[https://www.realvnc.com/en/connect/download/viewer/ RealVNC viewer]].
** Input <code>localhost:##</code> in the server address bar, where <code>##</code> corresponds to the last two digits of your port.

[[image:vncviewer.png]]

==== FastX Method (alternative) ====
FastX offers a potentially smoother experience compared to VNC, especially with multiple concurrent users.
* Download the [https://www.starnet.com/fastx/current-client FastX client] and:
** Start FastX.
** Click '+' to establish a new connection.
** Provide the Connection Name, host (squiggles.rcc.mcw.edu), and your RCC username.
** Start a session by clicking '+' and using the command <code>/etc/X11/xinit/xinitrc</code>.

[[File: FastX_config.png]]

=== Troubleshooting ===

;'''VNC Black Screen Issue'''
:If you encounter a black screen after logging into VNC, it could be due to the Anaconda Python environment interfering with the session. To resolve this issue, deactivate Anaconda Python using the command:
:<code>conda deactivate</code>

;'''Identifying Active Users'''
:To compile a list of users with active VNC sessions, which aids in monitoring current access to the VNC service, execute:
:<code>ls -l /tmp/.X11-unix</code>
:This information can be used to oversee session activity and ensure that resources are allocated efficiently.

;'''Terminating a VNC Session'''
:For situations where session termination is necessary, you can directly close a VNC session through the terminal or opt for manual termination if the direct method is insufficient. To directly terminate a session, use:
:<code>vncserver -kill :xx</code>
:Replace <code>:xx</code> with your session number.

:For manual termination, proceed to remove the session files with:
:<code>rm -f /tmp/.Xxx-lock</code>
:<code>rm -f /tmp/.X11-unix/Xxx</code>
:Ensure to replace <code>Xxx</code> with the correct session identifier. This allows for the removal of stuck or unresponsive sessions that cannot be closed normally.

;'''Alternative Solution: Identifying Active Sessions'''
:Identifying sessions created by a specific user can be a strategic approach to session management, offering an alternative to manual session termination. This method is particularly useful for identifying and removing only unnecessary or problematic sessions. Use the following command, replacing <code><username></code> with the actual username:
:<code>ps -ef | grep <username></code>
:This will list all processes related to the specified user. You can then terminate unwanted sessions by killing the process IDs:
:<code>kill -9 <PID></code>
:Where <code><PID></code> is the process ID obtained from the output of the previous command.

:To check the environment variables active during a VNC session, which can help in troubleshooting further issues, view the VNC environment log:
:<code>cat ~/vnc_environment.log</code>

Squiggles research computer server

2024-03-13T15:08:47Z

Vahab: /* Troubleshooting */

=== Introduction ===
"Squiggles" is a dedicated research computer server tailored for the analysis and storage of MEG, Neurophysiology, and Epilepsy data. This guide outlines how to connect using either the recommended FastX connection or the traditional VNC method.

=== Access Requirements ===
==== RCC Account ====

* An RCC (Research Computer Server) account is necessary to access "Squiggles".
* Register for an account at [https://docs.rcc.mcw.edu/user-guide/accounts/ MCW-Infoscope's Research Computing Center].
* If prompted, select "others" and then "squiggles" to specify the server you wish to access.
* Account approval generally takes 1-3 days. For any issues, contact Help-RCC at <help-rcc@mcw.edu>.

=== Login to Squiggles ===
'''Choosing a User Port:''' Each user is allocated a specific port number. New users should pick a port number (##) not already in use:

{| class="wikitable"
|-
! scope="col"|User
! scope="col"|Port
|-
|Jeff Stout
|5910,5911
|-
|Joe Heffernan
|5912
|-
|Candida Ustine
|5914
|-
|Manoj Raghavan
|5913
|-
|Chad Carlson
|5915
|-
|Chris Anderson
|5916
|-
|Serena Thompson
|5917
|-
|Patrick Bauer
|5918
|-
|Jeff Binder
|5919
|-
|Leo Fernandino
|5920
|-
|Lisa Conant
|5921
|-
|Aqil Izadysadr
|5922
|-
|Nick Guzowski
|5923
|-
|Zack Harper
|5924
|-
|Bill Gross
|5925
|-
|Michelle Kassel
|5926
|-
|Greg McQuestion
|5927
|-
|Monica Keith
|5928
|-
|Priyanka Shah
|5929
|-
|Vahab Youssofzadeh
|5931
|-
|Songhee Kim
|5935
|-
|Cameron J Stewart
|5992
|}
===== SSH Tunneling =====
* '''PowerShell Method (Mac/Linux/Windows):''' In a bash shell, terminal, or Windows PowerShell, execute the following to set up an SSH tunnel for the VNC Viewer:
<code>ssh -L 59##:localhost:59## USER@squiggles.rcc.mcw.edu</code>
where USER is your rcc user account and ## is the selected port number

* '''PuTTY (Windows):'''
[https://www.chiark.greenend.org.uk/~sgtatham/putty/ Download PuTTY] for SSH tunneling and refer to the images below for configuration:

PuTTY is an open-source software used for SSH Tunneling (or SSH Port Forwarding).

[[File:Putty config1.PNG]]
[[File:Putty config2 tunnel.PNG]]

=== Starting a Session and Connecting to Squiggles ===
Ensure you've established an SSH tunnel before proceeding with either the VNC or FastX methods.

==== VNC Method (preferred) ====
* '''Creating & Accessing a VNC Session''':
** VNC sessions initialize automatically upon boot-up.
** If issues occur, manually initiate a session using: <code>vncserver :## -geometry 1900x1200</code>, where <code>##</code> is your specific port number.
** Access the session using the [[https://www.realvnc.com/en/connect/download/viewer/ RealVNC viewer]].
** Input <code>localhost:##</code> in the server address bar, where <code>##</code> corresponds to the last two digits of your port.

[[image:vncviewer.png]]

==== FastX Method (alternative) ====
FastX offers a potentially smoother experience compared to VNC, especially with multiple concurrent users.
* Download the [https://www.starnet.com/fastx/current-client FastX client] and:
** Start FastX.
** Click '+' to establish a new connection.
** Provide the Connection Name, host (squiggles.rcc.mcw.edu), and your RCC username.
** Start a session by clicking '+' and using the command <code>/etc/X11/xinit/xinitrc</code>.

[[File: FastX_config.png]]

=== Troubleshooting ===

;'''VNC Black Screen Issue'''
:If you encounter a black screen after logging into VNC, it could be due to the Anaconda Python environment interfering with the session. To resolve this issue, deactivate Anaconda Python using the command:
:<code>conda deactivate</code>

;'''Identifying Active Users'''
:To compile a list of users with active VNC sessions, which aids in monitoring current access to the VNC service, execute:
:<code>ls -l /tmp/.X11-unix</code>
:This information can be used to oversee session activity and ensure that resources are allocated efficiently.

;'''Terminating a VNC Session'''
:For situations where session termination is necessary, you can directly close a VNC session through the terminal or opt for manual termination if the direct method is insufficient. To directly terminate a session, use:
:<code>vncserver -kill :xx</code>
:Replace <code>:xx</code> with your session number.

:For manual termination, proceed to remove the session files with:
:<code>rm -f /tmp/.Xxx-lock</code>
:<code>rm -f /tmp/.X11-unix/Xxx</code>
:Ensure to replace <code>Xxx</code> with the correct session identifier. This allows for the removal of stuck or unresponsive sessions that cannot be closed normally.

;'''Alternative Solution: Identifying Active Sessions'''
:Identifying sessions created by a specific user can be a strategic approach to session management, offering an alternative to manual session termination. This method is particularly useful for identifying and removing only unnecessary or problematic sessions. Use the following command, replacing <code><username></code> with the actual username:
:<code>ps -ef | grep <username></code>

Squiggles research computer server

2024-03-13T15:00:02Z

Vahab: /* Troubleshooting */

Squiggles research computer server

2024-03-13T14:42:37Z

Vahab: /* Troubleshooting */

Squiggles research computer server

2024-03-13T14:40:34Z

Vahab: /* Troubleshooting */

Squiggles research computer server

2023-11-15T16:43:27Z

Vahab: /* SSH Tunneling */

Squiggles research computer server

2023-11-15T16:42:31Z

Vahab: /* SSH Tunneling */

Squiggles research computer server

2023-11-14T20:13:26Z

Vahab: /* Troubleshooting */

Squiggles research computer server

2023-11-14T20:13:02Z

Vahab: /* Troubleshooting */

Squiggles research computer server

2023-11-14T20:12:45Z

Vahab: /* Troubleshooting */

Squiggles research computer server

2023-11-14T20:12:25Z

Vahab: /* Troubleshooting */

Squiggles research computer server

2023-11-14T20:11:27Z

Vahab: /* Troubleshooting */

Squiggles research computer server

2023-11-14T20:11:07Z

Vahab: /* Troubleshooting */

Squiggles research computer server

2023-11-14T20:10:27Z

Vahab: /* Troubleshooting */

Squiggles research computer server

2023-11-14T20:07:40Z

Vahab: /* Troubleshooting */

Squiggles research computer server

2023-11-14T20:06:31Z

Vahab: /* Troubleshooting */

Squiggles research computer server

2023-11-14T20:06:05Z

Vahab: /* Troubleshooting */

Squiggles research computer server

2023-11-14T20:04:58Z

Vahab: /* Troubleshooting */

Squiggles research computer server

2023-11-14T20:04:21Z

Vahab: /* FastX Method */

Squiggles research computer server

2023-11-14T20:03:57Z

Vahab: /* VNC Method */

Squiggles research computer server

2023-11-14T20:03:01Z

Vahab: /* SSH Tunneling */

Squiggles research computer server

2023-11-14T20:01:38Z

Vahab: /* SSH Tunneling */

Squiggles research computer server

2023-09-20T15:12:46Z

Vahab:

Squiggles research computer server

2023-09-20T15:12:29Z

Vahab:

Squiggles research computer server

2023-08-31T18:53:44Z

Vahab: /* Troubleshooting */

Squiggles research computer server

2023-08-31T18:52:46Z

Vahab: /* Login to Squiggles */

Squiggles research computer server

2023-08-31T18:52:23Z

Vahab:

Squiggles research computer server

2023-08-31T18:49:33Z

Vahab: /* RCC Account */

=== Introduction ===
"Squiggles" is a dedicated research computer server designed for the analysis and storage of MEG, Neurophysiology, and Epilepsy data. This guide elucidates the steps to connect using either the recommended FastX connection or the traditional VNC method.

=== Access Requirements ===
==== RCC Account ====

* To use "Squiggles", an RCC (Research Computer Server) account is required.
* Register for an account at [https://docs.rcc.mcw.edu/user-guide/accounts/ MCW-Infoscope's Research Computing Center].
* If prompted, select "others", then choose "squiggles" to specify the desired server.
* Account approval typically takes between 1-3 days. If you encounter any issues, please contact Help-RCC at <help-rcc@mcw.edu>.

=== Login to Squiggles ===
'''Choose User Ports:''' Each user has a dedicated port number for login. New users should select a sport number (##) that is not taken by other users:

{| class="wikitable"
|-
! scope="col"|User
! scope="col"|Port
|-
|Jeff Stout
|5910,5911
|-
|Joe Heffernan
|5912
|-
|Candida Ustine
|5914
|-
|Manoj Raghavan
|5913
|-
|Chad Carlson
|5915
|-
|Chris Anderson
|5916
|-
|Serena Thompson
|5917
|-
|Patrick Bauer
|5918
|-
|Jeff Binder
|5919
|-
|Leo Fernandino
|5920
|-
|Lisa Conant
|5921
|-
|Aqil Izadysadr
|5922
|-
|Nick Guzowski
|5923
|-
|Zack Harper
|5924
|-
|Bill Gross
|5925
|-
|Michelle Kassel
|5926
|-
|Greg McQuestion
|5927
|-
|Monica Keith
|5928
|-
|Priyanka Shah
|5929
|-
|Vahab Youssofzadeh
|5931
|-
|Songhee Kim
|5935
|-
|Cameron J Stewart
|5992
|}

===== SSH Tunneling =====
* ''' Power Shell Method (for Mac/Linux/Windows): ''' In a bash shell, terminal, or Windows PowerShell, execute the following to set up an SSH tunnel for the VNC Viewer:
<code>ssh -N -L 59##:localhost:59## squiggles.rcc.mcw.edu</code>

* ''' Putty (for Windows): '''
[https://www.chiark.greenend.org.uk/~sgtatham/putty/ Download Putty] for SSH tunneling, and follow the below images for configuration:

PuTTY is an open-source software for SSH Tunneling (or SSH Port Forwarding).

[[File:Putty config1.PNG]]
[[File:Putty config2 tunnel.PNG]]

=== Create a new Session and Connecting to Squiggles ===
Before proceeding with either the VNC or FastX methods, ensure you've established an SSH tunnel

==== VNC Method ====
* '''Creating & Accessing a VNC Session''':
** VNC sessions are initialized automatically during boot-up.
** If issues arise, manually start a session with: <code>vncserver :## -geometry 1900x1200</code>, replacing <code>##</code> with your specific port number.
** For access, employ the [[https://www.realvnc.com/en/connect/download/viewer/ RealVNC viewer]].
** In the server address bar, input <code>localhost:##</code>, where <code>##</code> matches the last two digits of your port.

[[image:vncviewer.png]]

==== FastX Method ====
FastX is potentially a more seamless alternative to VNC, especially when handling many simultaneous users.
* Fetch the [https://www.starnet.com/fastx/current-client FastX client] and then:
** Launch FastX.
** Press '+' to set up a new connection.
** Enter Connection Name, host (squiggles.rcc.mcw.edu), and your RCC username.
** To begin a session, tap '+' and use the command <code>/etc/X11/xinit/xinitrc</code>.

[[File: FastX_config.png]]

=== Troubleshooting ===
* '''VNC Black Screen''': Experiencing a black screen after VNC login? Ensure you've deactivated Anaconda Python prior. Command: <code>conda deactivate</code>.
* '''Persistent VNC Issues''': Switch to the FastX method.
* '''Killing a VNC session''': In terminal, <code>vncserver -kill :xx/</code>. For manual termination:
<pre>
rm -f /tmp/.Xxx-lock
rm -f /tmp/.X11-unix/Xxx
</pre>
* '''Identifying Active Users''': Command <code>ls -l /tmp/.X11-unix</code>.

Squiggles research computer server

2023-08-31T18:49:16Z

Vahab: /* RCC Account */

=== Introduction ===
"Squiggles" is a dedicated research computer server designed for the analysis and storage of MEG, Neurophysiology, and Epilepsy data. This guide elucidates the steps to connect using either the recommended FastX connection or the traditional VNC method.

=== Access Requirements ===
==== RCC Account ====

* To use "Squiggles", an RCC (Research Computer Server) account is required.
* Register for an account at [[https://docs.rcc.mcw.edu/user-guide/accounts/ MCW-Infoscope's Research Computing Center]].
* If prompted, select "others", then choose "squiggles" to specify the desired server.
* Account approval typically takes between 1-3 days. If you encounter any issues, please contact Help-RCC at <help-rcc@mcw.edu>.

=== Login to Squiggles ===
'''Choose User Ports:''' Each user has a dedicated port number for login. New users should select a sport number (##) that is not taken by other users:

{| class="wikitable"
|-
! scope="col"|User
! scope="col"|Port
|-
|Jeff Stout
|5910,5911
|-
|Joe Heffernan
|5912
|-
|Candida Ustine
|5914
|-
|Manoj Raghavan
|5913
|-
|Chad Carlson
|5915
|-
|Chris Anderson
|5916
|-
|Serena Thompson
|5917
|-
|Patrick Bauer
|5918
|-
|Jeff Binder
|5919
|-
|Leo Fernandino
|5920
|-
|Lisa Conant
|5921
|-
|Aqil Izadysadr
|5922
|-
|Nick Guzowski
|5923
|-
|Zack Harper
|5924
|-
|Bill Gross
|5925
|-
|Michelle Kassel
|5926
|-
|Greg McQuestion
|5927
|-
|Monica Keith
|5928
|-
|Priyanka Shah
|5929
|-
|Vahab Youssofzadeh
|5931
|-
|Songhee Kim
|5935
|-
|Cameron J Stewart
|5992
|}

===== SSH Tunneling =====
* ''' Power Shell Method (for Mac/Linux/Windows): ''' In a bash shell, terminal, or Windows PowerShell, execute the following to set up an SSH tunnel for the VNC Viewer:
<code>ssh -N -L 59##:localhost:59## squiggles.rcc.mcw.edu</code>

* ''' Putty (for Windows): '''
[https://www.chiark.greenend.org.uk/~sgtatham/putty/ Download Putty] for SSH tunneling, and follow the below images for configuration:

PuTTY is an open-source software for SSH Tunneling (or SSH Port Forwarding).

[[File:Putty config1.PNG]]
[[File:Putty config2 tunnel.PNG]]

=== Create a new Session and Connecting to Squiggles ===
Before proceeding with either the VNC or FastX methods, ensure you've established an SSH tunnel

==== VNC Method ====
* '''Creating & Accessing a VNC Session''':
** VNC sessions are initialized automatically during boot-up.
** If issues arise, manually start a session with: <code>vncserver :## -geometry 1900x1200</code>, replacing <code>##</code> with your specific port number.
** For access, employ the [[https://www.realvnc.com/en/connect/download/viewer/ RealVNC viewer]].
** In the server address bar, input <code>localhost:##</code>, where <code>##</code> matches the last two digits of your port.

[[image:vncviewer.png]]

==== FastX Method ====
FastX is potentially a more seamless alternative to VNC, especially when handling many simultaneous users.
* Fetch the [https://www.starnet.com/fastx/current-client FastX client] and then:
** Launch FastX.
** Press '+' to set up a new connection.
** Enter Connection Name, host (squiggles.rcc.mcw.edu), and your RCC username.
** To begin a session, tap '+' and use the command <code>/etc/X11/xinit/xinitrc</code>.

[[File: FastX_config.png]]

=== Troubleshooting ===
* '''VNC Black Screen''': Experiencing a black screen after VNC login? Ensure you've deactivated Anaconda Python prior. Command: <code>conda deactivate</code>.
* '''Persistent VNC Issues''': Switch to the FastX method.
* '''Killing a VNC session''': In terminal, <code>vncserver -kill :xx/</code>. For manual termination:
<pre>
rm -f /tmp/.Xxx-lock
rm -f /tmp/.X11-unix/Xxx
</pre>
* '''Identifying Active Users''': Command <code>ls -l /tmp/.X11-unix</code>.

Squiggles research computer server

2023-08-31T18:47:59Z

Vahab: /* RCC Account */

=== Introduction ===
"Squiggles" is a dedicated research computer server designed for the analysis and storage of MEG, Neurophysiology, and Epilepsy data. This guide elucidates the steps to connect using either the recommended FastX connection or the traditional VNC method.

=== Access Requirements ===
==== RCC Account ====
* To utilize "Squiggles", an RCC (Research Computer Server) account is mandatory.
* Register for an account on [[https://docs.rcc.mcw.edu/user-guide/accounts/ MCW-Infoscope's Research Computing Center]].
* If prompted, choose "others" followed by "squiggles" to indicate the server of interest.
* The process takes 1-3 days. If having an issue contact Help-RCC <help-rcc@mcw.edu>

=== Login to Squiggles ===
'''Choose User Ports:''' Each user has a dedicated port number for login. New users should select a sport number (##) that is not taken by other users:

{| class="wikitable"
|-
! scope="col"|User
! scope="col"|Port
|-
|Jeff Stout
|5910,5911
|-
|Joe Heffernan
|5912
|-
|Candida Ustine
|5914
|-
|Manoj Raghavan
|5913
|-
|Chad Carlson
|5915
|-
|Chris Anderson
|5916
|-
|Serena Thompson
|5917
|-
|Patrick Bauer
|5918
|-
|Jeff Binder
|5919
|-
|Leo Fernandino
|5920
|-
|Lisa Conant
|5921
|-
|Aqil Izadysadr
|5922
|-
|Nick Guzowski
|5923
|-
|Zack Harper
|5924
|-
|Bill Gross
|5925
|-
|Michelle Kassel
|5926
|-
|Greg McQuestion
|5927
|-
|Monica Keith
|5928
|-
|Priyanka Shah
|5929
|-
|Vahab Youssofzadeh
|5931
|-
|Songhee Kim
|5935
|-
|Cameron J Stewart
|5992
|}

===== SSH Tunneling =====
* ''' Power Shell Method (for Mac/Linux/Windows): ''' In a bash shell, terminal, or Windows PowerShell, execute the following to set up an SSH tunnel for the VNC Viewer:
<code>ssh -N -L 59##:localhost:59## squiggles.rcc.mcw.edu</code>

* ''' Putty (for Windows): '''
[https://www.chiark.greenend.org.uk/~sgtatham/putty/ Download Putty] for SSH tunneling, and follow the below images for configuration:

PuTTY is an open-source software for SSH Tunneling (or SSH Port Forwarding).

[[File:Putty config1.PNG]]
[[File:Putty config2 tunnel.PNG]]

=== Create a new Session and Connecting to Squiggles ===
Before proceeding with either the VNC or FastX methods, ensure you've established an SSH tunnel

==== VNC Method ====
* '''Creating & Accessing a VNC Session''':
** VNC sessions are initialized automatically during boot-up.
** If issues arise, manually start a session with: <code>vncserver :## -geometry 1900x1200</code>, replacing <code>##</code> with your specific port number.
** For access, employ the [[https://www.realvnc.com/en/connect/download/viewer/ RealVNC viewer]].
** In the server address bar, input <code>localhost:##</code>, where <code>##</code> matches the last two digits of your port.

[[image:vncviewer.png]]

==== FastX Method ====
FastX is potentially a more seamless alternative to VNC, especially when handling many simultaneous users.
* Fetch the [https://www.starnet.com/fastx/current-client FastX client] and then:
** Launch FastX.
** Press '+' to set up a new connection.
** Enter Connection Name, host (squiggles.rcc.mcw.edu), and your RCC username.
** To begin a session, tap '+' and use the command <code>/etc/X11/xinit/xinitrc</code>.

[[File: FastX_config.png]]

=== Troubleshooting ===
* '''VNC Black Screen''': Experiencing a black screen after VNC login? Ensure you've deactivated Anaconda Python prior. Command: <code>conda deactivate</code>.
* '''Persistent VNC Issues''': Switch to the FastX method.
* '''Killing a VNC session''': In terminal, <code>vncserver -kill :xx/</code>. For manual termination:
<pre>
rm -f /tmp/.Xxx-lock
rm -f /tmp/.X11-unix/Xxx
</pre>
* '''Identifying Active Users''': Command <code>ls -l /tmp/.X11-unix</code>.

Squiggles research computer server

2023-08-31T18:47:39Z

Vahab: /* RCC Account */

=== Introduction ===
"Squiggles" is a dedicated research computer server designed for the analysis and storage of MEG, Neurophysiology, and Epilepsy data. This guide elucidates the steps to connect using either the recommended FastX connection or the traditional VNC method.

=== Access Requirements ===
==== RCC Account ====
* To utilize "Squiggles", an RCC (Research Computer Server) account is mandatory.
* Register for an account on [[https://docs.rcc.mcw.edu/user-guide/accounts/ MCW-Infoscope's Research Computing Center]].
* If prompted, choose "others" followed by "squiggles" to indicate the server of interest.
* The process takes 1-3 days. If having an issue contact Help-RCC <help-rcc@mcw.edu> for help

=== Login to Squiggles ===
'''Choose User Ports:''' Each user has a dedicated port number for login. New users should select a sport number (##) that is not taken by other users:

{| class="wikitable"
|-
! scope="col"|User
! scope="col"|Port
|-
|Jeff Stout
|5910,5911
|-
|Joe Heffernan
|5912
|-
|Candida Ustine
|5914
|-
|Manoj Raghavan
|5913
|-
|Chad Carlson
|5915
|-
|Chris Anderson
|5916
|-
|Serena Thompson
|5917
|-
|Patrick Bauer
|5918
|-
|Jeff Binder
|5919
|-
|Leo Fernandino
|5920
|-
|Lisa Conant
|5921
|-
|Aqil Izadysadr
|5922
|-
|Nick Guzowski
|5923
|-
|Zack Harper
|5924
|-
|Bill Gross
|5925
|-
|Michelle Kassel
|5926
|-
|Greg McQuestion
|5927
|-
|Monica Keith
|5928
|-
|Priyanka Shah
|5929
|-
|Vahab Youssofzadeh
|5931
|-
|Songhee Kim
|5935
|-
|Cameron J Stewart
|5992
|}

===== SSH Tunneling =====
* ''' Power Shell Method (for Mac/Linux/Windows): ''' In a bash shell, terminal, or Windows PowerShell, execute the following to set up an SSH tunnel for the VNC Viewer:
<code>ssh -N -L 59##:localhost:59## squiggles.rcc.mcw.edu</code>

* ''' Putty (for Windows): '''
[https://www.chiark.greenend.org.uk/~sgtatham/putty/ Download Putty] for SSH tunneling, and follow the below images for configuration:

PuTTY is an open-source software for SSH Tunneling (or SSH Port Forwarding).

[[File:Putty config1.PNG]]
[[File:Putty config2 tunnel.PNG]]

=== Create a new Session and Connecting to Squiggles ===
Before proceeding with either the VNC or FastX methods, ensure you've established an SSH tunnel

==== VNC Method ====
* '''Creating & Accessing a VNC Session''':
** VNC sessions are initialized automatically during boot-up.
** If issues arise, manually start a session with: <code>vncserver :## -geometry 1900x1200</code>, replacing <code>##</code> with your specific port number.
** For access, employ the [[https://www.realvnc.com/en/connect/download/viewer/ RealVNC viewer]].
** In the server address bar, input <code>localhost:##</code>, where <code>##</code> matches the last two digits of your port.

[[image:vncviewer.png]]

==== FastX Method ====
FastX is potentially a more seamless alternative to VNC, especially when handling many simultaneous users.
* Fetch the [https://www.starnet.com/fastx/current-client FastX client] and then:
** Launch FastX.
** Press '+' to set up a new connection.
** Enter Connection Name, host (squiggles.rcc.mcw.edu), and your RCC username.
** To begin a session, tap '+' and use the command <code>/etc/X11/xinit/xinitrc</code>.

[[File: FastX_config.png]]

=== Troubleshooting ===
* '''VNC Black Screen''': Experiencing a black screen after VNC login? Ensure you've deactivated Anaconda Python prior. Command: <code>conda deactivate</code>.
* '''Persistent VNC Issues''': Switch to the FastX method.
* '''Killing a VNC session''': In terminal, <code>vncserver -kill :xx/</code>. For manual termination:
<pre>
rm -f /tmp/.Xxx-lock
rm -f /tmp/.X11-unix/Xxx
</pre>
* '''Identifying Active Users''': Command <code>ls -l /tmp/.X11-unix</code>.

Squiggles research computer server

2023-08-31T18:45:37Z

Vahab: /* Connecting to Squiggles */

=== Introduction ===
"Squiggles" is a dedicated research computer server designed for the analysis and storage of MEG, Neurophysiology, and Epilepsy data. This guide elucidates the steps to connect using either the recommended FastX connection or the traditional VNC method.

=== Access Requirements ===
==== RCC Account ====
* To utilize "Squiggles", an RCC (Research Computer Server) account is mandatory.
* Register for an account on [[https://docs.rcc.mcw.edu/user-guide/accounts/ MCW-Infoscope's Research Computing Center]].
* If prompted, choose "others" followed by "squiggles" to indicate the server of interest.
* Adhere to the ensuing steps to kickstart a new session and gain remote access to Squiggles.

=== Login to Squiggles ===
'''Choose User Ports:''' Each user has a dedicated port number for login. New users should select a sport number (##) that is not taken by other users:

{| class="wikitable"
|-
! scope="col"|User
! scope="col"|Port
|-
|Jeff Stout
|5910,5911
|-
|Joe Heffernan
|5912
|-
|Candida Ustine
|5914
|-
|Manoj Raghavan
|5913
|-
|Chad Carlson
|5915
|-
|Chris Anderson
|5916
|-
|Serena Thompson
|5917
|-
|Patrick Bauer
|5918
|-
|Jeff Binder
|5919
|-
|Leo Fernandino
|5920
|-
|Lisa Conant
|5921
|-
|Aqil Izadysadr
|5922
|-
|Nick Guzowski
|5923
|-
|Zack Harper
|5924
|-
|Bill Gross
|5925
|-
|Michelle Kassel
|5926
|-
|Greg McQuestion
|5927
|-
|Monica Keith
|5928
|-
|Priyanka Shah
|5929
|-
|Vahab Youssofzadeh
|5931
|-
|Songhee Kim
|5935
|-
|Cameron J Stewart
|5992
|}

===== SSH Tunneling =====
* ''' Power Shell Method (for Mac/Linux/Windows): ''' In a bash shell, terminal, or Windows PowerShell, execute the following to set up an SSH tunnel for the VNC Viewer:
<code>ssh -N -L 59##:localhost:59## squiggles.rcc.mcw.edu</code>

* ''' Putty (for Windows): '''
[https://www.chiark.greenend.org.uk/~sgtatham/putty/ Download Putty] for SSH tunneling, and follow the below images for configuration:

PuTTY is an open-source software for SSH Tunneling (or SSH Port Forwarding).

[[File:Putty config1.PNG]]
[[File:Putty config2 tunnel.PNG]]

=== Create a new Session and Connecting to Squiggles ===
Before proceeding with either the VNC or FastX methods, ensure you've established an SSH tunnel

==== VNC Method ====
* '''Creating & Accessing a VNC Session''':
** VNC sessions are initialized automatically during boot-up.
** If issues arise, manually start a session with: <code>vncserver :## -geometry 1900x1200</code>, replacing <code>##</code> with your specific port number.
** For access, employ the [[https://www.realvnc.com/en/connect/download/viewer/ RealVNC viewer]].
** In the server address bar, input <code>localhost:##</code>, where <code>##</code> matches the last two digits of your port.

[[image:vncviewer.png]]

==== FastX Method ====
FastX is potentially a more seamless alternative to VNC, especially when handling many simultaneous users.
* Fetch the [https://www.starnet.com/fastx/current-client FastX client] and then:
** Launch FastX.
** Press '+' to set up a new connection.
** Enter Connection Name, host (squiggles.rcc.mcw.edu), and your RCC username.
** To begin a session, tap '+' and use the command <code>/etc/X11/xinit/xinitrc</code>.

[[File: FastX_config.png]]

=== Troubleshooting ===
* '''VNC Black Screen''': Experiencing a black screen after VNC login? Ensure you've deactivated Anaconda Python prior. Command: <code>conda deactivate</code>.
* '''Persistent VNC Issues''': Switch to the FastX method.
* '''Killing a VNC session''': In terminal, <code>vncserver -kill :xx/</code>. For manual termination:
<pre>
rm -f /tmp/.Xxx-lock
rm -f /tmp/.X11-unix/Xxx
</pre>
* '''Identifying Active Users''': Command <code>ls -l /tmp/.X11-unix</code>.