Jupyter Notebook good first issues

The goal is to transform a static graphic from a blog post into a dynamic, interactive chart. This chart will be powered by a dataset stored within the repository and will be updatable over time, potentially hosted on a new website for the RMC repository.

This issue proposes optimizing job submission by pre-constructing 'beads' during job construction time instead of at submission time. This change aims to reduce serialization costs and alleviate bottlenecks on the critical submission path.

This issue reports the presence of invalid imagery, likely due to null metadata, specifically around "NULL island" coordinates. The problem might stem from STAC metadata or the image generation process, with a slight preference towards a STAC metadata issue.

This issue requires verifying how the STAC ingester handles existing entries, specifically if it performs an INSERT or UPSERT. The goal is to ensure that all updated metadata, including URL and identifier changes, is correctly propagated to the STAC database. Additionally, it calls for the deletion of cleaned-up entries from STAC, referencing related issues for context.

This issue requests that the 'multiview-stitcher' software be made available through the conda-forge package repository. This would simplify installation and management for users who rely on conda for their Python environments.

Netlify is mandating an update to the site's build image to a newer, supported version before January 2026. The issue proposes that a maintainer with Netlify access should perform this update to minimize the risk of build breakage, though a contributor is willing to assist if necessary.

This issue requests a review of the codebase to identify instances where the term "job" is used. The goal is to replace "job" with "workload" in any context where the latter is deemed more appropriate, aiming for clearer and more precise terminology.

The user is requesting the addition of release dates for Qiskit versions on the release notes pages. They found this information helpful for quickly determining if they have the latest version and for understanding the timeline of bug fixes relative to their code execution.

The user is requesting clarification on a statement in the IBM Quantum documentation regarding Qiskit Function workloads. The current text implies that the UI's workload table only shows Qiskit Runtime workloads, and suggests using `job.status()` for Qiskit Function status. The request is to explicitly state that the UI will not display function-related jobs and to clarify the meaning of 'currently' or remove the suggestion if it's not applicable.

This issue proposes adding a CI check to automatically detect and flag external links to IQP (quantum.cloud.ibm.com) that incorrectly include '/en/'. The goal is to prevent these broken links from being merged and to guide contributors towards using relative links for internal documentation and learning resources.

This issue addresses missing metadata (front matter) in several Qiskit SDK API documentation files. The fix involves adding an 'else' clause to a script that generates this metadata and determining how titles and descriptions will be automatically generated. The goal is to ensure this metadata is present and enforced by CI.

The release notes for Qiskit Runtime and Provider currently link to the top of the current version's release notes page, which can be disorienting for users. The request is to update these links to directly point to the specific historical release header (e.g., version .20) within the release notes documentation.

This issue requests an expansion of the documentation to include details on how to use the `meas_type` option for `SamplerV2` and `EstimatorV2`. The contributor will work with another user to add a description and code examples specifically for the 'kerneling' functionality.

This project aims to track the evolution of gendered and respectful language on English Wikipedia by analyzing changes in the usage of specific deprecated and preferred terms over time on policy-relevant pages. It involves data collection, text processing, statistical analysis to measure usage shifts, and visualization of findings.

The homr tool incorrectly merges staffs grouped by square brackets into a single part, treating them as grand staff braces. This leads to an incorrect number of parts in the MusicXML output, especially for ensemble scores where brackets are used to group instruments within a section. The issue persists for two-staff brackets, while three-staff brackets have been partially fixed.

A specific test (`test_parallel_paths_match_serial_per_path`) is failing on Windows CI environments when using pytensor version 3.2.3. The issue is not reproducible locally and might stem from an upstream pytensor problem with function serialization/deserialization. Further investigation, including bisecting pytensor versions, is needed to pinpoint the root cause.

This issue proposes an enhancement to allow the system to load data from multiple input file formats simultaneously, such as JSON, IOD, and UK, instead of being restricted to a single format. This is necessary for enabling multi-station orbit determination by combining data from various sources.

This issue reports that some nodes are experiencing missed inference events, suggesting a potential bug within the system. The root causes are unknown and likely multifaceted, requiring community investigation and collaboration to identify and resolve.

This issue proposes an enhancement to the default deviation calculation. Currently, it's fixed at 3000, but the suggestion is to make it dependent on the baudrate, specifically `max(3000, baudrate/4)`, as smaller deviations are often nonsensical at higher baudrates.

This issue proposes improving the user experience for displaying the mayor's information on the Councillor page. Currently, the mayor's details feel "shoehorned" in, and the suggestion is to rename the navigation item to better reflect the content. Additionally, the mayor's card should be visually separated from the councillors' cards for clarity and to simplify the codebase.

This issue requests the implementation of numerous fishing games for a comparison study, with each game to be implemented for a single deal. The list is categorized into 'Simple' and 'More complicated' games, with some already completed or nearly finished.

This documentation issue requests an update to clarify that the 'uv' tool must be installed prior to following environment setup instructions. It also asks for a direct link to 'uv' installation to improve user experience.

The MLflowLogger in PyTorch Lightning crashes when logging model checkpoints because MLflow's artifact path validation is stricter than Lightning's ModelCheckpoint. This prevents valid Python Path objects and common filename patterns used by Lightning from being accepted as artifact paths by MLflow, causing runtime errors when `log_model` is enabled.

This issue addresses deprecation warnings within the project's test suite to prevent future failures. The goal is to fix existing warnings and also to filter out any warnings that are outside of the project's control or are false positives, ensuring a cleaner test output. Several specific warnings have already been resolved, with one remaining to be addressed.

The user is experiencing intermittent failures in their CI environment when Dask attempts to read HTTP bytes. The traceback indicates an issue within Dask's HTTP byte reading functionality, specifically when fetching data ranges and encountering a mismatch between the requested and received byte counts.

This issue requests the transfer of 'microstructures' related to 'metallic grain structures' from a source (HTO) to a core system. It also involves the deletion of specific individuals. The linked image and term 'metallic grain structures' suggest a focus on material science or a related domain.

This issue proposes adding a new "Market Trends" visualization to the Bitcoin Stats tab, as the current section is a placeholder. The goal is to introduce a meaningful chart that complements existing dashboard metrics without duplication, and the team is open to suggestions on metrics, visualization types, and data sources.

This project aims to quantify controversy and protection dynamics on policy-sensitive Wikipedia pages by analyzing protection events and correlating them with edit bursts. The goal is to create a reproducible dataset and dashboard that illustrate how protection is used as a moderation tool, focusing on specific sensitive topics.

This issue requests the creation of an email redirect in Cloudflare for the 'alerts@civicdashboard.ca' address. The goal is to ensure that any replies sent to this non-existent email address are forwarded to a Gmail account, preventing bounce-back errors and facilitating communication.

The user finds that the default Matplotlib cycler with only three colors is insufficient for their needs. They are requesting an increase in the number of distinct colors available in the default color cycle.