How do I access drive inside my code
Your drive is automatically mounted inside every notebook and job as '/drive'
Your drive is automatically mounted inside every notebook and job as '/drive'
Notebook starts can take 5- 7 minutes. The main driver behind this is the time it takes for a cloud instance to be ready.
Jobs are essentially programs that will execute in the background. The state of a job goes from Submitted to Execution in progress to Executed or Execution Failed
Environments are anaconda environments that you can attach to a job. They are managed as conda yaml files that you can edit and must comply with the conda yaml format. E.g. https://github.com/binder-project/example-conda-environment/blob/master/environment.yml
Each job must have an environment attached to it. In the job settings, there is an environment dropdown. Make sure to create the environment first for the job and then attach.
We use credit card as a means to verify real users. We can't afford to have duplicate or fake accounts since we provide real value in terms of tools and compute.
Each credit is worth a minimum of 2 and maximum of 5 hours. So for Creator Plus, 40 GPU Credits would a minimum provide 80 GPU hours and a maximum of 200 GPU hours.
You can upgrade to Creator Plus or Creator Pro. Creator Plus gives you 40 GPU credits and 100 CPU credits for $22/month and Pro gives you 80 GPU Credits and 200 CPU credits for $44/month. Most of our users never exceed Pro limits. If you do, we are happy to discuss your use case.