Skip to content

Getting Help

How to request technical support? You have multiple options, please choose what fits you the best:

Current List of Known Issues

Check if your problem has been documented already. There is a list of known technical issues available.

Slack

Ask using Slack. If you haven't, please join the Neocortex Slack Organization. After you get into the Neocortex Slack, use any of the channels available to you:

  • Your project channel: in format #x00-lastname, is a private project channel for you and your team members, as well as the Neocortex and Cerebras team members, so all the project team members can brainstorm as needed and also request help from the Neocortex and/or Cerebras teams. In this example, "x" is one of the CFP cohorts (a, b, c, d), "00" is the project id, and "lastname" is the last name of your project PI.
  • #ai-projects: Public channel to discuss AI/ML-related subjects. All the AI/ML project team members can write in this channel, and all the AI/ML researchers will get the messages. You will get invited here if your project is on the AI/ML track.
  • #sdk-projects: Public channel to discuss SDK/HPC-related subjects. All the SDK/HPC project team members can write in this channel, and all the SDK/HPC researchers will get the messages. You will get invited here if your project is on the SDK or WFA tracks.

When writing the message in Slack, please describe the problem and include the information to reproduce any issues you might be having.

Email the Neocortex team

Email us at neocortex@psc.edu. Please describe the problem and include the information to reproduce any issues you might be having.

Neocortex Office hours

Bring your questions to an "office hour" session, in which you would be meeting with both Neocortex and Cerebras team members. You can request as many if these (30 minutes) sessions as needed.

To request a session per project, follow the appropriate link based on your project type:

While scheduling the session, please describe the problem and include the information to reproduce any issues you might be having.

Information for Reproducing the Issue

Please, describe the problem and include the details required for reproducing the issue as if you were explaining it to a new teammate. You can take a look at the Here is an example of what to include:

  • When is the issue happening?
  • Location of the code
  • Location of the input data
  • Script used for running the job
  • Sample output showing the problem
  • What is the expected output?
  • What is happening instead?