mk.bcgsc.ca No paid content found

A music artist network is a map where each artist is a node and each link represents a relationship between two artists, usually "listeners of one also listen to the other." On artistpath.cc you explore this map by entering two artists and tracing the chain of connections between them, then reading the visualization to see which links are strongest. It works best when you want to understand why two musicians feel related, or to discover artists that sit between two styles you already like. The connections reflect real listener behavior on Last.fm, not genre labels or historical influence, so treat them as a picture of audience taste rather than an objective ranking.

How an artist network is built

The network has two ingredients:

• Nodes — individual artists.
• Edges — links between artists, weighted by how often the same listeners play both.

Last.fm is a music tracking and recommendation service: it records what people scrobble (log) as they listen, and it publishes "similar artist" relationships derived from that listening data. When many listeners of Artist A also listen to Artist B, the two get connected. Stack thousands of these pairwise relationships together and you get a graph you can traverse.

Because the data comes from listening behavior, an edge means "these audiences overlap," not "these artists sound the same" or "one influenced the other." A shared link can come from genre, era, mood, playlist habits, or pure coincidence in a niche fanbase.

Finding a path between two artists

A path is the sequence of artists connecting your start point to your end point. A short path (one or two hops) suggests the two artists share a close audience; a long path means you have to travel through several intermediate tastes to get from one to the other.

On artistpath.cc the workflow is:

1. Enter a starting artist in the first field.
2. Enter a destination artist in the second field.
3. Run the path search. The tool walks the Last.fm-derived graph looking for a chain of connections.
4. Read the result as an ordered list of artists from start to finish.
5. Open the visualization to see the same chain as a graph, with the intermediate artists as nodes and the links between them as edges.

The expected result is a route like Artist A → Artist B → Artist C → Artist D, where each arrow is a supported similarity link. If no route appears, the two artists may simply sit in disconnected parts of the listener graph.

What to check after you get a path

• Length — how many hops did it take? Fewer hops generally means closer audience overlap.
• Intermediate artists — these are the bridge points. They are often the most interesting discovery, because they connect two worlds you already listen to.
• Link strength — where the tool shows it, a stronger link means more shared listeners, so that step is more meaningful than a weak one.

Reading the visualization

The graph view turns the path into something you can scan at a glance. Nodes are artists, edges are connections, and the shape of the chain tells a story:

Use the visualization to spot hubs. An artist that appears in many paths is a connector — a good candidate to explore if you want to move between genres.

Using the network to discover artists

The practical payoff is discovery through shared connections:

• Pick two artists you like and find the path between them. The artists in the middle are natural next listens.
• Follow a hub artist's links outward to see what else its audience plays.
• Compare a short path and a long path between the same pair to see which intermediate artists change.

For example, if you like two artists from different scenes and the path runs through a third name you have never heard, that third artist is the bridge your taste is already reaching toward.

Limits to keep in mind

• Connections reflect listener behavior, not objective genre, quality, or influence.
• Last.fm data skews toward users who actively scrobble, so popular and niche artists are represented unevenly.
• A missing path does not mean two artists are unrelated — it means the current data does not connect their audiences.
• A strong link is a statement about shared listeners, not a claim that the artists sound alike.

In stainless steel fabrication, design means engineering the part so it can actually be made: setting dimensions, material grade, joint and weld details, finish and tolerances, then checking that the workshop can cut, form, weld and finish it as drawn. It is not graphic design or product styling. This stage matters whenever you need a bespoke stainless item — a frame, tank, duct, pipework run or enclosure — and it usually starts from your sketch, sample or drawing rather than a finished CAD model.

What the design stage covers

Design work in a fabrication shop turns an idea into instructions the workshop can follow. That normally includes:

• Geometry and dimensions — overall sizes, bend radii, hole positions, and how parts fit together.
• Material grade — which stainless grade suits the environment (for example a grade chosen for corrosion resistance or for weldability). The fabricator should confirm the grade rather than assume it.
• Joint and weld details — where seams run, whether welds are visible or dressed, and how access is provided for the welder.
• Finish — the surface treatment required, such as a brushed, polished or other finish, and which faces are cosmetic.
• Tolerances — how accurate the finished part must be, since tighter tolerances generally mean more work.

How design decisions affect manufacture and cost

Most cost and lead-time differences between two apparently similar parts come from design choices, not from the amount of steel:

A design that is easy to weld and finish is usually cheaper and faster than one that only looks simple on paper.

Typical design-to-manufacture workflow

1. Brief or sketch — you provide a drawing, sketch, photo or sample, plus what the part must do.
2. Design review — the fabricator checks feasibility, suggests changes, and confirms grade, finish and tolerances.
3. Agreed drawing — a dimensioned drawing or model is signed off before cutting starts.
4. Fabrication — cutting, forming, welding and finishing to the agreed drawing.
5. Inspection — the finished part is checked against the drawing and finish specification.

The design review step is where most problems are caught cheaply, before any material is cut.

Common design mistakes that cause delays

• Missing dimensions, or dimensions that do not add up.
• No material grade specified, or a grade that is hard to weld or form.
• Finish left undefined, so the workshop guesses.
• No tolerance stated, leading to disagreement at inspection.
• No allowance for weld distortion on large or thin panels.
• Cosmetic faces not marked, so they get scratched during handling.

Questions to ask a fabricator at the design stage

• Which grade do you recommend for this environment, and why?
• Can this be made as drawn, or would a small change reduce cost or lead time?
• Which faces are cosmetic, and how will you protect them?
• What tolerance can you hold, and how will it be checked?
• Will welds be visible, dressed or hidden?
• What do you need from me before you can quote and start?

Getting clear answers to these before fabrication begins is the practical way to avoid rework and unexpected cost.

The Iroquois Indian Museum in Howes Cave, New York, is an educational institution whose stated purpose is to foster understanding of Iroquois culture by using Iroquois art as a window into that culture. In practice, that means a visit is organized around original work by Iroquois artists—both traditional and contemporary—rather than around a conventional timeline of historical objects. The approach suits anyone who wants to encounter Haudenosaunee (Iroquois) culture as something living and currently being made, not only as history.

The mission, stated plainly

The museum describes itself as "an educational institution dedicated to fostering understanding of Iroquois culture using Iroquois art as a window to that culture." Two things follow from that sentence:

• Art is the method, not just the subject. The exhibits are built to teach culture through the work, so the art carries the interpretation.
• The frame is Iroquois-specific. This is not a general Native American collection; the focus is the Iroquois (Haudenosaunee) peoples and their artists.

What "art as a window" actually means

Using art as the interpretive lens changes what you look at and how you look at it. A painting, basket, carving, or piece of beadwork can carry:

• Continuity — designs, materials, and techniques passed down across generations.
• Change — how artists respond to new materials, markets, and ideas over time.
• Voice — the artist's own perspective on identity, community, and history, in their own words rather than only through a curator's label.

Because the museum's collection spans both traditional and contemporary Iroquois work, the two are shown as connected rather than as "past" versus "present." A contemporary piece and an older one can be read as part of the same ongoing practice.

What a visitor can expect

Based on the museum's own description of its purpose, plan for:

• Original Iroquois art across media and periods, including work by living artists.
• Cultural context connecting the art to Haudenosaunee history, values, and present-day communities.
• An educational framing — the institution positions itself as educational first, so expect interpretive material rather than a purely aesthetic gallery experience.

The museum is located in Howes Cave, NY, in the Schoharie County area of upstate New York — Iroquois homelands region — which gives the visit a geographic as well as cultural context.

Why art instead of only historical objects

Art does something a case of artifacts often cannot: it shows a culture thinking and making decisions now. A historical object answers "what was made?" An artwork by a named Iroquois artist can answer "what is this artist saying, and to whom?" That shift keeps the culture from being frozen at a single moment and puts Iroquois people in the position of authors of their own representation.

Practical notes before you go

• Check current hours, admission, and exhibition schedule directly with the museum, since these change seasonally and are not fixed in the source material here.
• Payment: the site lists PayPal among its payment platforms; confirm accepted methods for admission when you book or arrive.
• Plan around the art. If you want the most from the visit, read the artist labels and interpretive text — that is where the "window" framing does its work.

If your interest is specifically in how a museum can teach a living culture through contemporary creative practice, this is the model to look at. If you want a broad survey of Native American nations across the continent, note that this museum's scope is deliberately narrower: the Iroquois, seen through their art.

JanusGraph is an open-source, distributed, transactional graph database built for graphs that grow past what a single machine can hold — the project targets hundreds of billions of vertices and edges across a multi-machine cluster. Choose it when you need Gremlin/TinkerPop querying, ACID or eventually consistent transactions, and the freedom to pick your own storage and index backends. Skip it if your graph fits comfortably on one node and you want the simplest possible operational footprint.

What JanusGraph actually is

JanusGraph is a graph database layer, not a storage engine. It handles graph semantics, transactions, and traversal execution, then delegates persistence and indexing to backends you choose. That design is the core of both its flexibility and its operational cost.

Key properties, per the project's own description:

• Distributed and scalable — elastic, linear scalability for growing data and user counts, with data distribution and replication for performance and fault tolerance.
• Transactional — supports thousands of concurrent users running complex traversals in real time, with ACID or eventually consistent transactions.
• Open source — fully open source under the Apache 2.0 license, governed by the Linux Foundation since 2017. The project states all functionality is free with no commercial license required.
• TinkerPop native — query with the Gremlin traversal language, serve with Gremlin Server, explore with the Gremlin Console.
• Analytics-capable — beyond online transactional processing (OLTP), it supports global graph analytics (OLAP) through an Apache Spark integration.

How it scales and stays available

The scaling story is the reason most teams evaluate JanusGraph:

This is a cluster-first design. If your workload is a few million edges on one server, that machinery is overhead you may not want.

Pluggable storage and indexing backends

JanusGraph does not lock you into a single storage engine. You select the backend that fits your existing infrastructure:

• Storage: Cassandra, HBase, Bigtable, ScyllaDB, and more.
• Indexing / full-text search (optional): Elasticsearch, Solr, or Lucene.

The practical consequence: your operational team keeps the database technology it already runs, and JanusGraph sits on top. The tradeoff is that you now operate both JanusGraph and its backends — more moving parts than a self-contained graph database.

Querying with Gremlin

JanusGraph is native to the Apache TinkerPop stack, so queries are written in Gremlin. The project's own quickstart shows the shape of a session:

$ bin/gremlin.sh
gremlin> graph = JanusGraphFactory.open('conf/janusgraph-inmemory.properties')
==>standardjanusgraph[inmemory:[127.0.0.1]]
gremlin> GraphOfTheGodsFactory.loadWithoutMixedIndex(graph, true)
==>null
gremlin> g = graph.traversal()
==>graphtraversalsource[standardjanusgraph[inmemory:[127.0.0.1]], standard]
gremlin> g.V().has('name','hercules').out('father').out('father').values('name')
==>saturn

What this demonstrates: you open a graph from a properties file, load a sample dataset, get a traversal source, then walk edges (out('father')) and read a property (values('name')). The in-memory configuration is for trying things out; production graphs point at a distributed backend instead.

Because Gremlin is a TinkerPop standard, skills and tooling transfer to other TinkerPop-compatible systems — useful if you want to avoid a proprietary query language.

When to choose JanusGraph — and when not to

Choose it when:

• Your graph is large enough that one machine is a real constraint (the project targets 100B+ vertices and edges).
• You need real-time traversals for many concurrent users, not just batch analytics.
• You want to reuse storage you already operate (Cassandra, HBase, Bigtable, ScyllaDB).
• You need multi-datacenter availability or hot backups.
• You want both OLTP and OLAP (via Spark) over the same graph.
• Open source under Apache 2.0 and vendor-neutral governance matter to you.

Look elsewhere when:

• Your graph fits on a single node and simplicity outweighs scale.
• You don't want to run and tune separate storage and index clusters.
• You need a query language other than Gremlin, or a fully managed service with no operational burden — the project describes a self-hosted, backend-pluggable architecture, not a hosted offering.

A quick way to decide

Ask two questions. First: does my graph exceed what one machine can serve, or will it soon? Second: does my team already run a supported backend like Cassandra or HBase? If both answers are yes, JanusGraph's distributed, transactional, backend-pluggable model fits well. If either is no, a single-node graph database will likely get you further with less operational cost.

To evaluate it hands-on, the Gremlin Console quickstart above runs against an in-memory graph, so you can test traversal patterns before committing to a cluster and a storage backend.

The Genome Sciences Center most commonly refers to the BC Cancer Genome Sciences Centre (GSC) in Vancouver, British Columbia—a genomics and bioinformatics research institute that combines high-throughput sequencing, cancer genomics, and computational tool development. It matters to you if you want to understand where widely used genome visualization software such as Circos came from, or if you need a working example of how a sequencing center turns raw genomic data into interpretable results.

What the Genome Sciences Center Is

The GSC is a research center built around large-scale genome sequencing and the computational analysis that follows it. Its work sits at the intersection of three activities:

• Sequencing at scale — generating genomic data from human and other organisms.
• Cancer genomics — studying how genomes change in cancer.
• Bioinformatics tool development — building software that makes genomic data analyzable and readable.

This combination is what distinguishes a genome sciences center from a purely clinical lab or a purely academic biology department: the center is organized around producing and interpreting genome-scale data.

Why It Shows Up in Discussions of Data Visualization

The GSC is closely associated with Martin Krzywinski, a scientist and designer known for genome data visualization. His work at the center produced tools and graphics that are now standard in genomics, most notably Circos, a circular layout tool for visualizing genomic relationships.

A concrete example from the center's own portfolio is "Circles of Life — Genomes Across Time," a comparison of the human genome with the genomes of chimp, dog, opossum, platypus, and chicken, designed by Krzywinski. This is a useful illustration of the center's role: it doesn't only sequence genomes, it also develops ways to show how genomes relate to one another across species.

That connection explains why a search for "genome sciences center" often surfaces visualization work. The center's identity includes making complex genomic data legible, not just generating it.

What Role It Plays in Genomics Research

The center's contribution is therefore twofold: it participates in genomics research directly, and it supplies methods and tools that other researchers use in their own work.

How to Access Its Public Resources

If you want to go beyond the description and actually use what the center produces:

1. Start with the visualization work — the center's design and visualization output, including Circos and related graphics, is the most directly reusable public-facing material.
2. Look for the software — tools such as Circos are distributed for use in your own genome data visualization tasks.
3. Check the research output — publications and project pages describe the sequencing and cancer genomics work in more detail.

The practical entry point for most readers is the tooling and visualization side, because that is what you can apply to your own data without being part of the center's research program.

When This Matters to You

• You are learning genomics and want to know where common visualization conventions come from.
• You need to visualize genome data and are evaluating Circos or similar circular layouts.
• You are researching the institution behind a specific tool or graphic.
• You want a model of how sequencing and visualization connect inside one research center.

If your interest is purely in sequencing technology or cancer biology, the center is one example among many; if your interest is in how genomic data gets turned into something you can see and interpret, its visualization legacy is the most relevant part.