Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Modify the ~/.ssh/config in your local workstation to include the following entries:

    Code Block
    languagenone
    Host *
       StrictHostKeyChecking no
    
    Host scu-login02
        HostName scu-login02.med.cornell.edu
        ServerAliveInterval 60
        TCPKeepAlive yes
  2. Connect to the WCM VPN Network

  3. Run the following from the terminal (Replace port with your lab’s specific port number herebelow):

    Code Block
    ssh node164 -L port:localhost:port
  4. Enter http://localhost:port within your local browser and authenticate using the credentials found in your cluster ~/cryo_creds file.

Connection - Windows

  1. Follow the SCU Windows SSH Forwarding guide found here (Update the port numbers):

  2. Enter http://localhost:port within your local browser and authenticate using the credentials found in your cluster ~/cryo_creds file.

...

  1. Modify the ~/.ssh/config in your local workstation to include the following entries:

    Code Block
    languagenone
    Host *
       StrictHostKeyChecking no
    
    Host pascal
        HostName pascal.med.cornell.edu
        ServerAliveInterval 60
        TCPKeepAlive yes
    
    Host node164
        Hostname node164.panda.pbtech
        ServerAliveInterval 60
        TCPKeepAlive yes
        ProxyCommand ssh -A -W %h:%p pascal.med.cornell.edu
  2. Run the following from the terminal (Replace port with your lab’s specific port number here):

    Code Block
    ssh node164 -L port:localhost:port
  3. Enter http://localhost:port within your local browser and authenticate using the credentials found in your cluster ~/cryo_creds file.

Connection - Windows

  1. Follow the SCU Windows SSH Forwarding guide found here (Update the port numbers):

  2. Enter http://localhost:port within your local browser and authenticate using the credentials found in your cluster ~/cryo_creds file.

...

It’s clear for most jobs whether they require GPUs or not (obviously, if the calculation has an input for the # GPUs available, then it needs GPUs!). However, some are ambiguous. We recommend you assume that the calculation does not require GPUs (if it’s not clear) and submit to `cryo-cpu`. If the calculation does require GPUs, it will almost immediately error out complaining about `pycuda`—if you see this, just clear the job and submit to a GPU-queue. If trial-and-error is not your thing, I’m sure the cryoSPARC documentation describes this in detail for each calculation 

...

Current Lab Ports
Anchor
ports
ports

Xin-Yun Huang 

39000

Crina Nimigean

39100

Alessio Accardi

39200

Olga Boudker

39300

Paul Riegelhaupt

39400

Joel Meyerson

39500

...

Contact

Please contact SCU@med.cornell.edu with any questions or concerns

...