mspass-team / mspass-team/mspass_tutorial

Raw cells instead of code cells in load_waveforms notebook

Open
#26 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Jupyter Notebook
Stars
9
Forks
8
PR merge metrics
No merged PRs in 30d

Description

These sections are raw cells and do not execute:

import boto3
from botocore.config import Config
from earthscope_sdk import EarthScopeClient

BUCKET = "earthscope-mseed-res-na3mtd4fq5kz7pntcyr1uh46use2a--ol-s3"

# Creates a daemon that renews the s3 client every 3400 s - timeout is 3600 s
s3_master_client = s3wp.ImmortalS3Client(dask_client)
s3_master_client.start()

Running this cell returns and error:

---------------------------------------------------------------------------
NameError                                 Traceback (most recent call last)
Cell In[6], line 8
      4 
      5 BUCKET = "earthscope-mseed-res-na3mtd4fq5kz7pntcyr1uh46use2a--ol-s3"
      6 
      7 # Creates a daemon that renews the s3 client every 3400 s - timeout is 3600 s
----> 8 s3_master_client = s3wp.ImmortalS3Client(dask_client)
      9 s3_master_client.start()

NameError: name 's3wp' is not defined

s3_master_client.status()

s3_master_client is never creates

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Open the load_waveforms notebook and inspect the cells containing the imports and s3wp.ImmortalS3Client(dask_client). Run those cells in order to reproduce the NameError. Done means the affected sections are executable code cells, the client is created, and s3_master_client.status() runs without that error.

Written by the indexing model from the issue text.

Assessment

Tech stack
jupyter-notebook, python
Domain
documentation
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.