Learn how to represent an unweighted undirected graph using an edge list. We build a sample graph with nodes and edges, then show the vertex list and edge list as tuples. See why storing indexes instead of node values makes lookups faster in constant time. Follow along as we list every connection without duplicates. This is the first in a series covering all four combinations of weighted and directed graphs with edge lists.

00:00 Introduction to Edge List Representation
00:56 Drawing a Sample Graph with Nodes
02:05 Adding Undirected Unweighted Edges
03:10 Graph as a Tuple of Vertex and Edge Lists
03:40 Building the Vertex List
04:24 Storing Nodes as Objects with Indexes
06:13 Creating the Edge List of Tuples
07:00 Listing Edges by Node Values
11:36 Limitations of Storing Node Values
12:30 Switching to Index-Based Edge List
14:08 Constant-Time Lookups with Indexes
16:54 Summary of the Edge List Method
17:16 Preview of Next Videos in the Series
17:44 Closing Remarks and Subscribe Request

=-=-=-=-=-=-=-=-=

Thanks for watching!

Find us on other social media here:

• https://www.NeuralLantern.com/social
• Twitter / X: https://x.com/NeuralLantern
• Rumble: https://rumble.com/c/c-3696939
• BitChute: https://www.bitchute.com/channel/pg1Pvv5dN4Gt
• Daily Motion: https://www.dailymotion.com/neurallantern
• Minds: https://www.minds.com/neurallantern/
• Odysee: https://odysee.com/@NeuralLantern:5

Please show your support!

• Buy me a coffee: https://ko-fi.com/neurallantern
• Subscribe + Sharing on Social Media
• Leave a comment or suggestion
• Subscribe to the Blog: https://www.NeuralLantern.com
• Watch the main “pinned” video of this channel for offers and extras

Hello there! Let’s talk about representing an unweighted,

undirected graph in your machine using an edge list representation.

Okay, so hopefully you watched my previous videos. If you haven’t, you might want to take a step back

and check them out. We talked about, you know, what is a graph? What are some basic rules and

terminology of a graph? Not graph and paper, but a graph. And we talked about representing paths

in graphs.

representing paths in graphs using either a list of nodes or a list of edges and we’re going to

take the edge list concept one step further and we’re going to actually just say this whole graph

is being represented as an edge list it’ll make sense in a little bit but uh so the first thing

i’m going to do is try to set up my stuff which is always set up wrong because i’m the one setting it

up and it always gets messed up okay so i got a graph paper and uh oh i got to make this other

thing full screen. Sorry.

um i’m going to draw a random graph just real fast so i’m going to do i don’t know just some random

nodes so remember a graph is a collection of nodes and edges doesn’t even have to have edges but you

know we’ll just say so we’re going to do that’s bad let me try one more time we’ll get that okay

so we get i’m trying to get this circle perfect because i’m gonna have to duplicate it rare okay

i’ve got a node here and i’m just going to give it an arbitrary value i’m going to say it’s got a 3

and then i’m going to duplicate it a few times just to make a graph that is a little bit

interesting so we have something uh something to kind of challenge us i guess so it’s not

incredibly boring um and then i’m going to change some of the values here and then well i’ll change

the next ones and then we’ll start looking at edges which edges do we want to make okay so

right now we’re just making a graph make this graph along with me if you want to or uh you

you know, after you.

to or uh you know after you think you understand do another graph on your own

okay so i’m gonna make some edges right now remember this is going to be an undirected

unweighted graph so the edges are just going to be lines they’re not going to have direction on

them and they’re not going to have weights on them i’m going to do a line over here i’m just

randomly doing lines doesn’t really matter um what we do exactly the point is going to be let’s

practice represented

be let’s practice representing this graph okay so i’m just making a random graph it’s kind of like

a little bit dense i don’t know um maybe i’ll just stop there and then i’ll add a wonky line just

just to prove we can be cool about this i don’t know we’ll do another one right here so it’s a

slightly more interesting graph okay so um that’s just a graph and uh what i’m going to do is i’m

going to say this is a, you know, an unweighted, oops, weighted.

oops waited undirected uh graph and we’re going to use the edge list of representation

i have spell check on this i really hope i do nope okay i guess i forgot to fix that months ago

all right so then the next thing we’re going to do is uh we’re going to look at the idea of like

how do we start with the edge list representation okay um the first thing i’m going to say is that

our graph

that the our graph in an edge list representation is a tuple just meaning it’s you know some things

put together if you know tuples encoding already uh the tuple is going to consist of a collection

of vertices and edges what’s going to be an edge list don’t make fun of my ease please

anyway so uh let’s do the first thing is going to be the vertex list so how do we represent the

vertex list or the node list well i’m just going to say that my vertex list v

to say that my vertex list v is equal to something and we’ll just put inside of this

some vertices so the easiest way when you’re kind of drawing this right now is i’m just going to

start putting the values of the node i’m going to say well here’s a three and uh i guess i could

sort them for whatever reason uh if we’re going to do binary search on them later but we’re not

going to i’m just going to maybe you know what i’ll go from left to right so that’ll make more

sense, just visually. So I’ll go from left to right. 3, 13, 6, 12.

3, 13, 6, 12, and a 15, and an 18.

You can see all of those are nodes, right?

Somebody stop me if I forgot a node.

Okay, here’s the thing though.

What are we actually storing in this vertex list?

You probably don’t want to store the node values.

I mean, you could be a little slow and dumb though,

but we want the option to be a little bit faster later

and also the option to turn these vertices into full classes,

like give them extra properties and whatever.

So what I’m going to say is that…

So what I’m going to say is that I’m writing down the number 3 and the number 13 here for you, but you should imagine in your code you would have an object of type vertex or node, like a full class, and you would basically be stuffing pointers inside of that vector, inside of that list.

I keep saying list. It is called an edge list representation, but you can probably imagine

that this could just as easily be a vector. If you’ve seen my other videos, you know what that is.

but uh so i want to be able to index this uh faster so for me personally i make this a vector

and not an actual list but we’re going to call it a list anyway so three should be a pointer

uh to a full node object uh smart pointer raw pointer whatever you want 13 should be a full

pointer to an entire uh entirely different node object with just 13 assigned as its uh template

type value because we’re making this a vector we can actually index

can actually index uh the nodes right so like this is like index 0 for the 3 node index 1 for the 13

node so i’m just going to put the indexes here whoops just to drive the point home a little

bit further so if i told you hey let’s do uh the node at index 2 you would know that is the node

that is in the very middle with the value of 6 because index 0 and 1 and 2 brings you to this

node right here um which is a 6 so this is going to this is going to help us later let me save this

Real fast, by the way.

let me save this real fast by the way i’m just going to do that okay so uh the next thing that

we need to do is uh make an edge list the edge list is really where it’s all at that’s really

where all the data is it’s going to tell us exactly where everything is or it’s going to

describe the whole graph pretty much so the edge list is another we’ll say that’s a list this could

be like a linked list or vector or whatever you want i’m just going to say it’s a linked list

and every item in the list is going to be another tuple so remember above the graph itself was a

tuple containing a vertex list and an edge list so the edge list is a list of tuples

meaning you know items bundled together for one tuple and then just like a list of those

so what i’m going to try to do is describe every single edge uh one by one using one tuple each

inside of the edge list so the first thing i’m going to do just you know to make this a little

little bit easier.

thing I want to do just you know to make this a little bit easier is I’m going to ignore the

indexes for the vertex list and I’m going to say let’s describe everything happening from the three

node outwards or just to every other node so the three node itself I’m going to look at its

connections from left to right so the three node let’s just start by putting a three here

maybe I should describe the legend real fast the tuples will basically be the start node

and then the end node

and then the end node and then the uh well the weight if there was a weight but we’re doing an

unweighted graph so it’s really just going to be a tuple of two items the other thing to keep

in mind is that because this is an undirected graph it really doesn’t make a difference what

node is the start node and what node is the end node you can just swap them and it’s totally fine

for me personally i’d rather you know sort before assigning the start node and end node that way

when i read the graph later it’s a little bit faster because i wouldn’t have to check in both

directions but

wouldn’t have to check in both directions but it really honestly doesn’t matter right now so

start node and end node so the start node here is 3 and the end node is going to be 13 so that’s the

first thing that we’re doing that’s the first tuple and then i’m going to say what else does

the 3 connect to it connects to the not the 6 it connects to the 12. okay so the 3 connects to the

12. again we could have said 12 comma 3 wouldn’t have mattered but i’m just going to try to keep

it sorted so then

keep it sorted so then what else does the three connect to it connects to the uh the 18 doesn’t

connect to the 15 and just confirm that if i’m looking at the three i can see three lines

touching it so that means okay there’s got to be three tuples for the for the e for the three so

i’m going to say three connects to the 18. and now i’ve described everything happened to do with the

three note i will simply continue let’s see should i do like a new line maybe i should try to do a

new line for every

try to do a new line for every start node so this is easier to look at okay so i’m going to do that

and i’m going to say the next line is we’ll start at the 13 this time so the 13 the 13 is also

connected to the 3 because it goes in both directions with an undirected graph but we

already described that connection with that first row so 3 comma 13 describes 13 comma 3 i don’t

want to duplicate edges so forget about that let’s look at what else 13 is connected to it’s connected

it to the six

connected to it’s connected to the six so I’m just going to put 13 comma 6 and then that’s the end of

the 13’s connections oh I could have used tabs for that hang on let me do that okay so now let’s look

at the six node six is not connected to the three it is connected to the 13 but we already described

the 13 6 connection in the previous row so forget that and then I’m just going to look to the right

So the 6 is connected to the 12 and the 15.

the 12 and the 15 12 and the 15 and also the 18 so i’m going to do 6 comma 12 maybe i’m going to

do a copy paste here real fast just to make it easier 6 12 and 6 15 and 6 18 so again all i’m

doing is describing you know what other nodes the current node is touching and i’m going to do that

using a tuple that just has one node and has another node and that’s pretty much it so when

we’re done with this

it so when we’re done with this uh we’re going to look at the 12 node 12 node it’s connected to

the six already handled it’s connected to the three it’s already handled and it’s connected

to the 18 not handled yet so i’m going to say 12 goes out to 18. okay then we’re going to look at

the 15 node 15 and 6 that’s already handled in that third row so forget that 15 and 18 that is

is not

15 and 18 that is not handled yet so we’re going to do 15.18 by the way this is one benefit of

going from left to right visually all i really have to do is just look my eyes to the right and

i’ll see nodes that i need to take care of and if i look my eyes to the left i’ll see nodes that i

already took care of if that makes sense so now that we’re done with the 15 let’s see we did 3 13

6 12 15 let’s just take care of the 18 if there’s anything left to take care of i can guarantee

there’s not going to be.

there’s not going to be because every node the 18 is the node on the farthest you know the furthest

to the right so everything on the left is already handled so we don’t even have to put anything for

the 18 node okay give me a second to clean up this graph real fast i think i want to maybe

move this up a little bit okay uh now here’s the thing though we’ve only named node values so if

we wanted to i don’t know let’s say check to see if the uh let’s say we have an edge we’re looking

Thank you.

let’s say we have an edge we’re looking at the 3 comma 13 edge and we’re asking now do both of

those nodes exist the edge describes these two nodes do they exist or uh maybe let’s look at

the three here and we want to figure out just you know what other nodes does three touch so we start

iterating through all the edges here how can we actually get a pointer to that node to manipulate

it in the code right now it’s okay because it’s a diagram but you know this is not very

diagram but you know this is not very good storing values directly in this notation in your code you

probably want to store pointer uh pointers there but maybe not necessarily smart pointers they take

a little bit of extra memory and it’s kind of cumbersome but um we could store an index into

this vertex list to make things a little bit faster let me show you what i mean but first i’m

going to duplicate this list that we just made already, duplicate it over here, and

over here and maybe i’ll label the first one and i’ll say so we already have start node and end

node i’m going to say e underscore by value so we’re storing the edge list by node values and

then here we’re going to store nodes by their index in the vertex list so what do i mean by

index well okay right here the first node that we’re mentioning is the three well look at the

three node in the vertex list it’s at index zero right so i’m just going to put a zero

zero right so i’m just gonna put a zero that’s it change it to an index then i look at the 13

that’s index one and then i look at the three again that’s index zero um and then the 12 is

index three and then the three again is index zero and the 18 is index five um if that was too fast

i’m sorry just rewind and play it back in slow motion i think this video is already getting way

too long so then i do the same thing for every single other tuple so the 13 node um that is

node um that is index one so i’m going to put a one there the sixth node is index two go on to

the next node so the sixth node is index two and then the 12 is index three and the six is two and

the 15 is actually four the six again is two the 18 is five move on to the 12 node here uh that’s

index 3, 18 node is index 5, and then

the 15

and then uh the 15 is index 4 and then 18 again is index 5 so now on you know on both sides like

in both of these edge lists uh i’m representing the graph it’s just that one can be a little bit

more efficient than the other uh for example if i was going to let’s just say i wanted to scan

every single edge in the graph well i could scan this list right here in linear time so linear time

based on the number of edges and every single time i see an edge i can jump directly to the

Corresponding.

jump directly to the corresponding vertex or node in constant time because i have an index

so for example let’s say uh you know this uh the sixth node um touching the 15 node so that

particular edge right there let me i want to be more interactive here how can i do this okay

uh suppose i want to do

612 node and so that’s going to be pointing to this edge right up here i want to see you know

what’s going on with both of those nodes well if i was looking at the value-based edge list

and i wanted to get a hold of let’s say the sixth node itself so i can like do something with that

vertex like delete it or move it or just whatever i would have to then scan the entire vertex list

i’d have to go you know this one this one this one this one this one until i eventually found

the corresponding value.

uh the corresponding value this wouldn’t really support duplicate values either

uh it would be kind of hard to do that but uh i’ve i’ve slowed down the program it’s linear

time based on the number of vertexes and if you’re already doing linear time based on the number of

edges this is like it’s technically still a scalable data structure but it’s not super fast

it could be faster on the other hand uh so like i just said uh sorry for repeating myself if we did

the index

the index based uh edge list it says two three here which is the 612 how can i find the sixth

node well i just look at index two and instead of scanning oh gosh hang on

i’m not as fast as i used to be okay dude there’s like did you see that uh

a whole bunch of pink dots everywhere now what have i done okay

So, uh…

so uh i’m looking at the 612 edge i see that the indexes are two and three that means in constant

time i can just jump directly to i guess i’ll put it in red in constant time index two right there

and index three right there i do not have to scan the vertex list or the vector i guess if it was a

vertex list like an actual linked list then i’d still have to scan because it’s linear time to do

it but if it’s a vector

But if it’s a vector or an array, I can just jump to an index in constant time, so it’s way faster.

So what I’m trying to say is that this representation is what you want to do in the code when it comes to, I don’t know, representing diagrams and stuff.

I don’t know. The one on the left is more human friendly.

So this is the basic idea for how to represent an unweighted and also undirected graph in the machine using the edge list method of representation.

i guess i’m going to cut the video i hope you learned a little bit of stuff and had

a little bit of fun in the next video i think i’m going to do uh weighted uh undirected graphs

and this i’m going to do four videos for this one representation type i’m going to do unweighted

undirected and then weighted and undirected and then unweighted and directed i’m gonna

do all four combinations all right see you in the next video thanks for watching

hey everybody thanks for watching this video again from the bottom of my heart i really appreciate it

i do hope you did learn something and have some fun if you could do me a please a small little

favor could you please subscribe and follow this channel or these videos or whatever it is you do

on the current social media website that you’re looking at right now it would really mean the

world to me and it’ll help make more videos and grow this community so we’ll be able to do more

videos, longer videos, better videos, or just I’ll be able to keep making videos in general.

just i’ll be able to keep making videos in general so please do do me a kindness and uh and subscribe

you know sometimes i’m sleeping in the middle of the night and i just wake up because i know

somebody subscribed or followed it just wakes me up and i get filled with joy that’s exactly what

happens every single time so you could do it as a nice favor to me or you could you could troll me

if you want to just wake me up in the middle of the night just subscribe and then i’ll i’ll just

wake up i promise that’s what will happen also uh if you look at the middle of the screen right now

you should see a QR code, which

screen right now you should see a QR code which you can scan in order to go to the website which

I think is also named somewhere at the bottom of this video and it’ll take you to my main website

where you can just kind of like see all the videos I published and the services and tutorials and

things that I offer and all that good stuff and if you have a suggestion for clarifications or

errata or just future videos that you want to see please leave a comment or if you just want to say

hey what’s up what’s going on you know just send

what’s going on? You know, just send me a comment, whatever. I also wake up for those in the middle

of the night. I get, I wake up in a cold sweat and I’m like, it would really, it really mean

the world to me. I would really appreciate it. So again, thank you so much for watching this video

and, um, enjoy the cool music as, as I fade into the darkness, which is coming for us all.

Thanks for watching!

The post How to Represent an Unweighted Undirected Graph with an Edge List appeared first on NeuralLantern.com.

Hey there, let’s talk about paths inside of a graph. We draw a directed weighted graph and compare node-based paths to edge-based paths. Node lists alone cannot tell which edge you took when parallel edges have different costs. Edge-based paths use tuples of start, destination and weight so every route is clear.

We also cover simple paths with no repeated edges or vertices, cyclic paths that start and end on the same node, and how a cycle proves the graph is cyclic. Then we explain DAGs, directed acyclic graphs, with examples that stay acyclic and ones that gain cycles.

This sets up algorithms for later videos. Leave a comment with topics you want next. Thanks for watching and please subscribe.

00:00 Introduction to Graph Paths
00:28 Drawing a Sample Graph
02:25 What is a Path
02:42 Node-Based Paths
03:27 Adding Weights and Parallel Edges
04:34 Example Paths with Different Costs
07:19 Edge-Based Paths
07:35 Representing Paths with Tuples
11:35 Order Matters in Directed Graphs
12:52 Simple Paths
15:34 Cyclic Paths
18:22 Directed Acyclic Graphs DAGs
19:08 Building a DAG Example
21:41 Adding a Cycle to Break the DAG
23:15 Conclusion and Future Videos

=-=-=-=-=-=-=-=-=

Thanks for watching!

Find us on other social media here:

• https://www.NeuralLantern.com/social
• Twitter / X: https://x.com/NeuralLantern
• Rumble: https://rumble.com/c/c-3696939
• BitChute: https://www.bitchute.com/channel/pg1Pvv5dN4Gt
• Daily Motion: https://www.dailymotion.com/neurallantern
• Minds: https://www.minds.com/neurallantern/
• Odysee: https://odysee.com/@NeuralLantern:5

Please show your support!

• Buy me a coffee: https://ko-fi.com/neurallantern
• Subscribe + Sharing on Social Media
• Leave a comment or suggestion
• Subscribe to the Blog: https://www.NeuralLantern.com
• Watch the main “pinned” video of this channel for offers and extras

Hey there, let’s talk about paths inside of a graph.

Okay, so first thing that I’ll say is you probably should have watched my other videos already so that you understand at least the basics of graphs or maybe you already know and you just came here for a little extra.

So let’s just draw a sample graph here.

I’m going to do like random nodes.

Let’s see what am I supposed to do.

I’m supposed to like full screen that.

I’m going to draw some random nodes with some random values inside of them.

So I’m just going to do like a three here.

Maybe like a three like that.

And then I’m going to duplicate this a few times.

So I’m going to go.

This is a valid graph.

It’s just not a connected graph as we talked about in my last video.

So I’m just going to do this.

I guess that’s okay.

I’m going to change all these numbers.

Even though your graph should be able to support duplicate values in the nodes,

it’s going to be really hard to explain.

So I’m just going to change all this stuff.

9 here and then like 22.

I think that’s probably good.

So I’m going to do this.

And this.

Okay.

So still a valid graph, but there’s no chance that we could have a path anywhere in this

entire graph.

anywhere in this entire graph so that sucks we could by the way do a path

with a undirected graph but I kind of feel like I want to do direction on all

the edges so let’s see let’s do direction and also weight I’m gonna like draw an

arrow here and arrow here there I’m gonna draw edges first in a way that it

like I could find a path almost anywhere I want so I’m just going to like draw a bunch of edges

maybe like another edge over here nope that’s wrong how about this maybe another edge going up

here and an edge going up here and an edge going down there I’m just going to draw a whole bunch

of edges in the hopes that we’ll have a decent graph with lots of path possibilities okay I guess

Oh, no, no, this is not a complete graph.

I’ve just drawn a graph where you can kind of get everywhere.

Okay, so, well, I mean, what is a path?

It’s just sort of like, you know, some sort of a representation of how do you get from

one start node to some destination node, like a map.

So the first thing that we could do is we could say, let’s make a path based on nodes.

I’m going to say node-based paths.

Actually, let me get rid of this and put it on the next slide.

We’ll do this, duplicate it, that way I have the original.

Let’s pretend that our path is going to be just a list of nodes that we travel through.

So I’m going to say node-based and we’ll have one path, we’ll say path1 and then path2,

maybe we’ll do like a second path.

well at first we might think this is totally fine but uh later on it’ll get confusing in terms of

which edge did we actually take so let me show you let me show you what i mean i’m first going

to add weights to all the edges so i’m just going to do like you know four and a three over here

and then like a one and a two little one and then like a six and then like a four i’m just adding

random weights or random costs to all of the edges and um then eventually let’s see when i

let’s see when I finish doing all of that eventually we can probably realize that we

could add more than one edge going from the same start to the same destination node but give it a

different weight so that we have a little bit more of a choice so suppose for the sake of argument

that we have this six and the four here the six can go to the four at a cost of four but maybe the

a cost of one. I don’t know why it’s there. I don’t know why the four is there. Also,

we’ll just say this is our graph. So you can have edges like this that go to the same start

and destination nodes, but have different weights. So a path that is based on nodes

doesn’t really have enough information to tell us which edge we took. Let me show you what I mean.

So suppose we want to get from node, I don’t know, node three, I’ll put an S here for start.

for start. And then I guess I’ll put a D for destination or donut. I’ll put a D there on

node number 22. So we’ll say we’re going to go from node three to node 22. So start and destination

a path based, sorry, a node based path, path one, we could say maybe let’s go from the three

to the six to the four to the 12 to the nine to the 22 and that tells you all the notes that

you would hop on another path could be let’s see that first path when we went from three one six

four twelve nine uh 22 when we go from the six to the four we could have a second path here

that goes from three to one to six to four but takes a different edge this is kind of what i’m

this is kind of what i’m trying to show you notice that we have two different paths i’m going to do

one in uh maybe red so it’s going to be three one six four so from three to one and then six

and then we’ll travel along that four edge once we get to the four we’ll go 12 and then once we

Then the other path, path number two, let’s say that we chose the other edge.

We chose the six to the four edge that only cost us one.

So it would kind of look the same for the most part, except when we finally get to that

other node, we’re actually going to be going this way, right?

And then we’re going to go up and then to the right and then down.

So if you look at this carefully for a little while, maybe pause the video.

These are actually two totally different paths with two totally different costs.

different costs. So, um, you know, the cost of the orange, let me write it in orange.

It’s going to be five plus one. So six, and then a seven there, and then a eight, nine there. And

then, uh, then I guess like a 15 there and then a 16 there. So the cost of the orange pass is going

to be 16. If we switch to the red path, the only difference is the choice of edge we took between

we took between the six and the four node.

So we would increase our cost by three.

So the red path would be a cost of 19.

But how can you tell the difference in a path

that is based on a node?

It doesn’t have enough information, right?

So what we’re gonna do instead

is we’re gonna use edge-based paths.

Edge-based paths.

In some places, you know, you can use node-based paths.

That’s totally fine.

fine but for me I’m going to say let’s do edge based paths edge based paths and now we just have

to figure out how to add that extra information into the path so going from the three to the one

we’re actually traveling along an edge right we’re traveling along that five edge so let’s just stick

a tuple in there a tuple meaning just a little collection of values for those of you in c++ if

items we’re going to use three item tuples tuples not always limited to three items it could be two

three four even probably one um or much more so i’m going to say let’s use a tuple that has three

items per item or tuple and we’ll just say that we specify the start node and then the destination

node so we start at three we go to one and then the weight of the edge that we choose to travel

but we’re putting enough information into our hop

that this can be considered an edge-based path.

So when we go to the one node,

we ended on the one node, sorry, we’ve gone to the one node.

We just ended there.

So we could start on the one node for the next tuple

because then we’re going to go to the,

what are we doing first, red?

I think we’re doing red first, yeah.

We go from the one node to the six nodes.

So I’m going to go comma six.

and then we choose which edge to travel along that’s just the one edge and so 161 means start

at the one node and at the six node and take the one weighted edge then do the same thing

again for the next tuple so we’re at the six now where are we going to go we’re going to go to the

four and then we choose the edge that costs four and then for the next tuple we’re on the four

I’m going to say 12 is the destination and which edge did we choose the two even though there’s

only one choice at least we have enough information for all edges in our entire path so then again

we’re at the 12 we’re going to go to the 9 so I’m going to put a common 9 there and then we choose

to take the edge that uh what was that cost six I can’t read anymore um let me actually just look

real fast six I guess I overrode it I’m just going to assume that it’s a six um I’ve got

I guess I could erase it real fast

or move it or something

okay let’s see what is that

yeah it’s a 6 okay

so we’re on the 12 we’re going to go to the 9

and we choose to take the edge that costs 6

then we’re on the 9

and we choose to go to the 22

using the edge that costs 2

and then this last thing doesn’t need to be done

because we have the entirety of the path

in our edge based list

So I’m actually just going to copy paste this entire path and stick it into the second path

because remember the only difference between the first path and the second path that we

chose is when we were going from 6 to 4 we chose the 1 edge instead of the 4 edge.

So now look at this, I can just change that 4 to a 1 and now we definitely have two different

paths and because we’re using edges to describe our path we can tell the difference.

You know in a computer program we would know exactly which edge to travel along or even

which edge to travel along or even just a user moving their finger along a graph or whatever.

So in my opinion, edge-based paths are a little bit better.

They’re also better because if you practice writing down edge lists like this,

then you get a lot closer to a representation of a graph in your machine called an edge list.

So in an edge list, oops, I put ed light.

I don’t know why I did that.

And now the computer’s not responding.

So my mistake is immortalized.

my mistake is immortalized. Edge list representation of a graph is basically a graph is equal to

a tuple where one item in the tuple is a list of vertices and another item in the tuple

is a list of edges. So if you learn how to do edge-based paths, then you’re already a step

closer to being able to represent a graph inside of your computer program in the machine.

So another thing that I want to point out is that since this graph has direction,

the order of the start node and the destination node absolutely matters for example if we have

this three comma one here indicating we start at three and we end at one well that means there must

be an edge that points from three to one otherwise this is an invalid path if for some reason

if for some reason let me get rid of this here there’s too much stuff on the screen

three this is invalid because it’s saying that we have to start at the one node and end at the three

node but the one node has no has no edge going to the three node so this is totally invalid

does that make sense i hope it makes sense to you if this was an undirected graph where every single

edge did not have direction then the order actually wouldn’t even matter you would just

to see if an edge existed.

So let’s see, we talked about different paths.

You know, typically you would want to choose

the lowest cost path,

but there are algorithms that we can use

in future videos to compute paths.

Let’s see, something called a simple path

is where every single edge in the path is distinct.

So for example, I don’t know,

let’s say we had like a really gross path here.

Let me get rid of, let me get rid of some of this.

Let me get rid of some of this.

Get rid of the oranges maybe.

So that this is a little slightly easier to read.

Let’s see.

Did we choose?

Oh, I have to fix this.

Let’s fix the three and then the one.

And then we chose the four.

So this is the red path indeed.

So a simple path is, nope, I accidentally erased like an extra edge or something.

So I got to do one from the four to the 12.

Okay.

to the 12 okay let me just do that real fast from the 4 to the 12. at a cost of 2. okay so a simple

path is something where you don’t repeat edges so i can also write down simple path here simple path

if this was not a simple path then we would just basically have to repeat an edge somewhere

so um if any of the edges or vertices were repeated this would not be a simple path so let me just i

would not be a simple path so let me just I don’t know let me just update this real fast let’s say

we do oh what should we do let’s do I don’t know when we go from three to one to six to four

let’s go back from four to six and then we’ll take the other edge back to four and then we’ll

go up to 12 so this will be like um not a simple path if we say gosh I should have written this

this down before i drew it three to one and then one to six and then six to four and then four back

to six okay so i’m going to add another tuple so starting at four going back to six and taking

that three edge i think is what we’re looking at and then another tuple to get back when we go from

six to four and then take the um one cost edge and then once we’re at four then we can go four

cost of two and then 12 to nine at a cost of six and then nine to 22 at a cost of two okay so

i mean i’m just saying you can make a path where you just repeat a whole bunch of the edges and

nodes and you’re just like going in a circle forever like whatever you really want it’s not

necessarily going to be an efficient path or something that an algorithm should produce

but you can have a path like that maybe your character is just going crazy in the game and

because we repeat stuff on the previous slide.

Since we did not repeat anything, this is a simple path.

Okay, let’s see.

Something else that I wanna talk about is a cyclic path.

A cyclic path is basically a path

where you start and end on the same node.

Being able to find a cyclic path in a graph

is a way that you can prove that the graph is itself cyclic.

is itself cyclic. Let me try to get rid of this here. Yeah, there we go. Okay, so just

pretend for the sake of argument that I’m just kind of looking around and I’m trying to find,

you know, some path that proves I can start at the same node and end on that node without

repeating edges. So let’s see. Right, so I’m going to do take the three and go to the six.

to the six and then so i want to try if i start on the three then i want to try to find a way to get

back to the three again so i go from three to six and then i can go from six to four

and then if i go from four to six over here i’m not repeating that edge going from six to four i’m

using a new edge from four to six and then i can go from six to three again not actually repeating

means I have found a cycle in the graph. Let me just describe this path real fast in terms of

edges. So we started on three. Oops. We started on three and then we went to six and it cost us three.

And then once we were on six, we went to four. So I’m going to go from six to four. And we chose

the edge that cost us four. And then once we were on the four, we just went backwards to the six.

four going to six and we took the edge that cost three once we were on six we took the six to three

edge so six to three whoops six to three edge and that cost us three yeah did I do that right

when we go from the three to the six in the beginning I wrote down a three but I should

have written down a two hopefully you cringed on my behalf right because I was I think that red

on the left side so my brain was looking at the three but we were really taking the arrow that

points down from the three to the six so there’s a two there let me just double check one more time

six to four at cost of four four to six at cost of three six two three at cost of three

so we have started and ended uh on the same node and therefore we have found a cycle in this graph

which means this graph is cyclic what is cyclic just means it’s a graph that has a cycle

It’s a graph that has a cycle anywhere inside of it.

So this is a cyclic graph.

Make sense?

Okay, why is this important?

Well, there’s kind of like a special type of graph called a DAG,

which means a directed…

Here, let me write this down real fast.

On the next slide, so that we don’t get confused.

On the next slide, I’m going to say we have a DAG

is basically a directed…

directed, acyclic graph. What does A mean when it’s in front of something? It just means it’s

not that thing. So acyclic means not cyclic and then graph. So in some algorithms you are required

to, you know, like have a DAG before you can even use the algorithm or if you’re being tested

somewhere. So let’s just start by, you know, drawing like a little bit of a graph and we’ll

have a graph that qualifies. So I have a little graph here. If it was empty,

I don’t know if you could call it a DAG or not. I think I would because it’s empty. It could be

directed. So we have like a graph here. I would call this a DAG because it’s a graph. We don’t

have any edges, but like I could assume that this would be a directed graph. But just to make this

a better example, let’s just say we have like two nodes here. And you could also probably assume

DAG because you could assume that there are no edges in this graph but if we did add an edge

a second from now then it would be directed not the best example but so let’s just add an edge here

oh actually let’s add an edge that’s undirected real fast from from two to six and then maybe

I’ll just kind of duplicate some of these we’ll do a couple more so I can just make this more

so ask yourself is this a DAG directed acyclic well there are no cycles that I can see in the

graph there’s no paths that you can find to kind of like end where you started but this is a it is

a graph and I don’t see any cycles but it’s not directed because these edges don’t have direction

so that means right away we have to upgrade every single edge to have direction so I guess I was

going to draw a bunch more edges and now I’m just going to only draw this one edge

So this is definitely a DAG if we just sort of do it like this, maybe another edge like this,

because I don’t know about you, but I cannot find any path that allows me to start and end

on the same node. Let’s just double check it. We’ll do the two. Can we find our way back to

the two? No, because there are no incoming edges to the two. All right, that’s good. Let me just

do a check here. What about the six? If we go out to the six, from the six to the four to the

6 from the 6 to the 4 to the 11 it would have been dangerous if we could get to the 2 but we

can’t even get to the 2 so that’s fine that means the 6 is okay we cannot find our way back there

the 4 we can go to the 11 but we can’t go any further we’re at a dead end we can’t even go to

the 6 that means the 4 can’t find its way back to itself where you can’t find a path that goes back

the 11 has only incoming edges so that’s automatically you know a dead end so all of

nodes qualify as we could not start and also end at that node with a single path so that’s good

that means this is a DAG a directed acyclic graph if you want to make this into not a DAG just figure

out how to add a path so that you end up with a cycle so what was the first thing we did the 2

goes to the 6 goes to the 4 goes to 11 then it’s a dead end we could either add an edge from 11 to 2

to make a cycle but that’s a little bit too easy right because if you see any pair of nodes

right because if you see any pair of nodes with arrows kind of pointing back and forth between the

two nodes then right away that alone is a cycle so I’m just going to maybe do an arrow or an edge

pointing from four to two then it doesn’t look so much like a cycle although it’s not too hard

to realize that there is a cycle in this graph in this graph so this is not a DAG let me show you

and then from four to two.

And therefore we would have a cycle.

So this whole graph is not considered acyclic.

This graph has a cycle.

And if we want to do an edge-based path,

we don’t have weights on this graph right now.

So we could describe the path as such.

We could say, start at two, go to six.

And if your edge list is of a graph

that doesn’t even have weight at all,

then you don’t really need that third item in the tuple.

item in the tuple you can just do a start node and a destination node this does kind of preclude

you from having parallel edges you know two different edges that point from the same start

node to the same end node so as i go from two to six and then from six to uh four and then from

four to two and then we have a cycle and that’s it okay i think this is all i really wanted to

talk about for this particular video in future videos we’re going to do algorithms and then

some others up already that have graph properties and connectedness and definitions and things like

that. So leave a comment asking about some algorithm or some property of a graph that

you might be interested in. Otherwise, thank you so much for watching this video. I hope you learned

a little bit of stuff. And I hope you had a little bit of fun. I’ll see you in the next video.

Yeah, I’m gonna go eat some cookies. No, I shouldn’t do that. But I’m still going to.

Hey everybody, thanks for watching this video again from the bottom of my heart.

I really appreciate it.

I do hope you did learn something and have some fun.

If you could do me a please, a small little favor, could you please subscribe and follow

this channel or these videos or whatever it is you do on the current social media website

that you’re looking at right now.

It would really mean the world to me and it’ll help make more videos and grow this community.

So we’ll be able to do more videos, longer videos, better videos, or just I’ll be able

better videos or just I’ll be able to keep making videos in general so please

do do me a kindness and and subscribe you know sometimes I’m sleeping in the

middle of the night and I just wake up because I know somebody subscribed or

followed it just wakes me up and I get filled with joy that’s exactly what

happens every single time so you could do it as a nice favor to me or you could

you control me if you want to just wake me up in the middle of the night just

subscribe and then I’ll just wake up I promise that’s what will happen also if

if you look at the middle of the screen right now you should see a qr code which you can scan

in order to go to the website which i think is also named somewhere at the bottom of this video

and it’ll take you to my main website where you can just kind of like see all the videos i

published and the services and tutorials and things that i offer and all that good stuff and

if you have a suggestion for uh clarifications or errata or just future videos that you want to see

Or if you just want to say, hey, what’s up?

What’s going on?

You know, just send me a comment, whatever.

I also wake up for those in the middle of the night.

I get, I wake up in a cold sweat and I’m like,

it would really, it really mean the world to me.

I would really appreciate it.

So again, thank you so much for watching this video

and enjoy the cool music as I fade into the darkness,

which is coming for us all.

so

Thank you.

I’m going to go ahead and get started.

Thank you.

The post Graph Paths Explained: Node vs Edge Based, Simple Paths, Cycles and DAGs appeared first on NeuralLantern.com.

Hello there. Lets talk about graphs and whether they are connected or not or maybe whether they are strongly connected versus weakly connected. We look at undirected graphs first and show what makes a graph connected meaning every node can reach every other node by a path. We add edges and check the connections step by step while also noting subgraphs. Then we switch to directed graphs and explain strongly connected versus weakly connected. Strongly connected follows the edge directions for every path. Weakly connected ignores the directions and checks if the graph would still be connected. Examples show how adding edges changes the status of the graph.

00:00 Introduction to Graph Connectedness
00:01 Drawing Nodes and a Disconnected Graph
01:56 Defining a Connected Graph
03:21 Introducing Subgraphs
04:48 Adding Edges to Create a Connected Graph
06:32 Adding Directions to Create a Directed Graph
08:03 Strongly Connected Versus Weakly Connected
08:34 Removing an Edge to Show Disconnection
09:29 Checking and Achieving Weak Connectivity
11:18 Adding Edges to Create a Strongly Connected Graph
13:20 Confirming the Strongly Connected Graph
13:32 Conclusion
14:17 Outro and Subscribe Request

=-=-=-=-=-=-=-=-=

Thanks for watching!

Find us on other social media here:

• https://www.NeuralLantern.com/social
• Twitter / X: https://x.com/NeuralLantern
• Rumble: https://rumble.com/c/c-3696939
• BitChute: https://www.bitchute.com/channel/pg1Pvv5dN4Gt
• Daily Motion: https://www.dailymotion.com/neurallantern
• Minds: https://www.minds.com/neurallantern/
• Odysee: https://odysee.com/@NeuralLantern:5

Please show your support!

• Buy me a coffee: https://ko-fi.com/neurallantern
• Subscribe + Sharing on Social Media
• Leave a comment or suggestion
• Subscribe to the Blog: https://www.NeuralLantern.com
• Watch the main “pinned” video of this channel for offers and extras

Hello there! Let’s talk about graphs and whether they’re connected or not or maybe whether they’re

strongly connected versus weakly connected versus not connected. You never know.

Okay, so hopefully you’ve seen my previous videos by now where we just talked about the basics of

paper here i’m just going to start drawing a graph remember graphs are nodes and edges where

the nodes are like little t-type data structures that can hold a specific type of value um so i’m

going to say our our nodes hold integers um i think i made that one too small that’s okay

and the edges uh could have weights or maybe not weights at all depending on if you have

a weighted or an unweighted graph so i’m just going to start duplicating my nodes a little bit

going to make a random graph. I need to probably change these values. Technically your graphs

should support duplicate values in the nodes and also the weights, but I don’t want to because

it’s easier to talk about the graph when all the values are distinct. So for starters, we have a

bunch of nodes and they’re not really connected to each other. Is this a valid graph? Yeah it is.

It’s just not a connected graph. So the terminology that we’re going to use for

undirected graphs meaning the edges don’t have direction is going to be connected or not you

know i usually just say a not connected graph or a disconnected graph so just basically like

connected or not connected okay so this is a not connected graph i’m going to say not connected

not cinnamon i’m thinking about food as usual

connected graph why is it not a connected graph well to define what does it mean to be a connected

graph it just means that every single node can find a path to every single other node

in an undirected graph so we can just double check this real fast we can say you know can

node number two find a path to uh you know let me put a question here let’s say we’re going to check

you should be checking all the nodes one by one by one to see if if the node in particular can

first node that can’t do it means the whole graph is not considered connected so you know two it

can’t reach one so that means it’s not a connected graph so this is not a connected graph because one

or more nodes violate the rule of you have to be able to reach every single other node okay so that

means if we want a connected graph we probably just have to start adding edges so I’m going to

go ahead and uh let me let me write the word connected here and then I can like either circle

cross it out. So right now we have no, this is not a connected graph. I’m going to start adding

edges. We’re going to stick with an undirected graph for now. So I’m going to connect two and one

and two and nine, maybe one and 13. Actually, you know what? I’m going to erase this edge

and maybe connect these over here. And the thing is, this is a valid graph that you’re looking at.

it’s just not a connected graph.

Some other terminology I didn’t mention in other videos

is that we can have subgraphs.

We have like a subgraph here and another subgraph here.

Those are basically just two different portions of the same graph

that appear to be connected within themselves.

So those are subgraphs.

You can probably tell right away that this is not a connected graph.

You can double check to be sure.

You know, it’s good to do things the hard way

so you don’t get the wrong answer

when you’re really trying to figure something out.

So let’s look at two.

So let’s look at two. Can two reach one? Yes. So that’s good. Can two reach nine? Yeah,

it just hops to one and then hops to nine. So two can reach one and also nine. That’s good.

Can two reach three? Nope. So this is still not a connected graph.

Okay, I’m going to add one more edge. And then we’ll just check again.

Where do you think I’m going to do it? Maybe if I add, I’ll add a funky edge going from 13 to like

to like nine or something just so it feels a little bit more awkward okay let’s check one by

one by one let me actually get rid of this edge on the previous slide so we can still say that’s

not connected let’s check one by one by one every node must be able to reach every single other

node so I’m gonna look at two and I’m gonna say all right two can it reach one yes can it reach

to nine. So that’s good. Can it reach three? Yeah, it can go from two to one to nine to 13

to three, and then it can reach three. And because we just saw that it went through 13 to reach three,

that means two can reach every single other node. This is going to be more important as a double

check when we have directed graphs in a second. So two is good. So the next thing you want to do is

the next thing you want to do is just move on to some other node and do the exact same process you

know can can nine reach a one yes okay it can reach a one can it reach a two yeah it goes through

the one can it reach the 13 yep can it reach the three yep okay so we just check every single

destination node starting at the node nine but here’s a little bit of a shortcut try to find a

node that is right next to a node that you know can reach everything and if the node in question

that previously connected node, vertex,

then we know that that node in particular is also connected.

So what I’m saying is the one,

instead of checking every single other node in the graph,

which might be really hard

if we have a whole bunch of nodes in our graph,

we’ll just ask, can the one reach the two?

Because if it can, the two can reach everything.

So that means the one actually can reach everything as well.

So the one can reach the two.

So the one is connected to everything.

the three, the three can reach the one and the one can reach everything. I’m doing things the

hard way on purpose just to prove a point. So the three can reach everything. The 13 can reach the

three in one hop. So the 13 can reach everything. The nine, it can reach the one and it can reach

the 13 in one hop. So the nine can also actually reach everything. So that means this is indeed a

the next thing that we’re going to do is add direction to our graph you know we could do like

more examples maybe leave a comment if you want me to do some super extra complicated examples for

just a undirected and connected graph i’m ignoring weight by the way because it doesn’t really matter

for these purposes so let’s upgrade our graph so uh maybe i should put a question mark here

that would have been a good idea we’re just asking you know is it connected or not

And I’m just going to start adding direction to every single edge.

Let’s see if I’m following my notes.

Single node, subgraphs, right?

Well, it wasn’t connected at first and then we started adding.

Okay, so that’s basically okay.

Let’s add direction to every single edge.

So every single edge has to have a direction

or every single edge has to have no direction.

You can’t really mix and match.

So I’m just going to go through every single edge and add a direction like this.

and you know to be fair I think I’ve said this in my other videos an undirected edge is kind of the

same thing as a directed edge going in or two directed edges going in both directions so this

3 and 13 what’s going on with my computer hello this 3 and 13 edge it would have kind of been the

same as just having two edges going in opposite directions so maybe I’ll just do that right now

for this huge weird edge I’m just going to put like an arrow over here instead of totally redrawing

Then I double check that every single edge has a direction so that I have a valid graph.

And now I can ask, is this connected or not?

Actually, when it comes to a directed graph, you don’t really have connected or not anymore.

You have strongly connected versus weakly connected.

Maybe I should just separate these words and then just kind of like move them.

So let’s get rid of this.

to this save this over here move it down so what am i talking about um well first let me remove an

edge real quick i’ll remove this edge right here so now we have two sub graphs in this graph you

can tell for sure if this was an undirected graph it would not be connected but now that we’re

dealing with direction we have to ask is it strongly connected versus weakly so what does

can every node reach every other node if you obey the direction of the edges so that’s clearly not

true there’s no edge at all that even connects this one and nine so it’s definitely not strongly

connected weakly connected on the other hand means if you temporarily ignore the direction

of the edges then could you consider the graph connected so if we pretended that there were no

arrows here would we think that it’s a connected graph if the answer is yes then it’s at least a

So this is not weakly connected because if this was an undirected graph, it’s not even connected at all.

So that sucks.

I’m going to go ahead and add another edge here.

So I’m going to add an edge from 2 to 9.

So the first thing is, oh, sorry, I have to add another edge.

Let me do from 1 to 13 for fun.

So now the first thing is, let’s check to see if this is a strongly connected graph.

node is unreachable by any other node so this is definitely not strongly

connected because all the other nodes would be would have to be able to reach

too alright so first thing you could do just to very quickly check is just look

at every single node and ask is it reachable you know by anything and then

after that you can do things the hard way so it’s not strongly connected what

about weakly connected if we ignore the direction of the graph sorry if we

then yeah, we could reach every single node from every other node. Let’s just double check that

real fast. I’m going to say, you know, the two node, if we’re ignoring direction, can it reach

the one? Yes. Can it reach the 13? Yes. The three? Yes. Can it reach the nine? Yes. So that means the

two node is sort of like weakly connected to every other node in the graph. Do the same thing for the

one node. Previously, we just said, you know, check everything one by one or use a shortcut.

one by one or use a shortcut. So I’m going to use the shortcut. The one node, if we ignore direction

can reach the two nodes. So I’m going to say the one is weakly connected, at least everything else.

I’m not even going to check to see if it’s strongly connected to everything else. I think the answer

is no, but we do the same thing for the 13. The 13 can reach the one pretty fast. The three can

reach the 13. The nine can reach the two. So every single node can weakly reach. That’s not an

a weakly connected graph. Okay, cool. How can we make this a strongly connected graph? Well,

we just have to add a bunch of edges. So that’s what I’m going to do. I’m going to kind of like

look at what is missing here. So we’ll ask the two, can the two reach and let’s obey the direction

of the edges again. Can the two reach the one? Yes. Can the two reach the 13? Yes. Can it reach

Yes, so that means right now the two is strongly connected to everything else.

So we’re on track for a strongly connected graph.

We then look at the one node and we realize that the one node,

it can reach the 13 and the three and it can also reach the nine,

but it can’t reach the two.

That’s one thing that was blocking us last time from saying strongly connected.

So we just have to add another edge if we want this to be a strongly connected graph.

We have to figure out how can we get the one to reach the two.

the 2 we can go through something if we want to that’s fine we can also just

write an edge that just goes back to the 2 but that’s I don’t know that’s kind of

boring I’m gonna make an edge that goes from 1 to 9 and then I’m gonna make an

edge that goes from 9 to 2 so looking at the 1 node it can now reach the 2 if we

go through the 9 so that’s good can the 1 reach the 9 yes can the 1 reach the 13

three yes okay so the one node can now reach every single other node so now we’re a little bit more

on track for a strongly connected graph look at the 13 node can it reach the one node um actually

yes if we go from 13 to 9 and then 2 and then 1 we can reach the one node since we know the one

node is connected to everything else we can now say that the 13 node is connected to everything

13 so i’ll say three is connected to everything the nine node can reach the two node which is

connected to everything so that means the nine node is also connected to everything and at this

point we now have a strongly connected graph it’s not weakly connected it’s stronger than that

any questions um so let’s see we added a bunch of uh edges i think maybe this is actually all we

need to do for this particular video because we’re just going to talk about connectedness

going to talk about connectedness about 15 minutes not too bad all right so i think i’m

going to leave it here drop a comment if you want to do way more complicated examples if you want to

provide me a sample graph that’s awful and i could just i don’t know in the sometime in the future i

could record a video about it um or just let me know your thoughts thank you so much for watching

this video i hope you had a little bit of fun and i hope you learned a little bit of stuff i’m outie

Patowdy.

Alright, let’s see.

I’m going to do this.

Whoa. Can you see that guy in the background?

Oh, shoot.

I’m just kidding.

I set that as the screensaver.

Hey, everybody.

Thanks for watching this video again from the bottom of my heart.

I really appreciate it.

I do hope you did learn something and have some fun.

If you could do me a please, a small little favor,

please subscribe and follow this channel or these videos or whatever it is you do on the current

social media website that you’re looking at right now. It would really mean the world to me and it’ll

help make more videos and grow this community. So we’ll be able to do more videos, longer videos,

better videos, or just I’ll be able to keep making videos in general. So please do me a kindness

and subscribe. You know, sometimes I’m sleeping in the middle of the night and I just wake up

or followed. It just wakes me up and I get filled with joy. That’s exactly what happens every single

time. So you could do it as a nice favor to me or you could you could troll me if you want to just

wake me up in the middle of the night. Just subscribe and then I’ll just wake up. I promise

that’s what will happen. Also if you look at the middle of the screen right now you should see a

QR code which you can scan in order to go to the website which I think is also named somewhere at

the bottom of this video and it’ll take you to my main website where you can just kind of like see

videos i published and the services and tutorials and things that i offer and all that good stuff

and uh if you have a suggestion for uh uh clarifications or errata or just future videos

that you want to see please leave a comment or if you just want to say hey what’s up what’s going on

you know just send me a comment whatever i also wake up for those in the middle of the night i get

i wake up in a cold sweat and i’m like it would really it really mean the world to me i would

it so again thank you so much for watching this video and enjoy the cool

music as as I fade into the darkness which is coming for us all

Thank you.

so

I’m going to go ahead and get started.

so

Yeah, I think I’m good.

Hello there.

Let’s talk about whether a graph is connected or not,

or maybe whether it’s strongly connected or weakly connected or not connected at all.

You never know.

The post Graph Connectedness Explained: Connected Strongly Connected and Weakly Connected appeared first on NeuralLantern.com.

Learn graph basics: nodes, edges, neighbors, adjacency. Undirected vs directed, unweighted vs weighted. Representations including edge list, adjacency list, and matrix. Great intro for computer science students.

00:00 Graph Basics Introduction
00:41 Nodes and Edges
01:20 Node and Edge Classes in C++
03:46 Simple Graph Examples
04:29 Adding Edges – Undirected Unweighted
05:26 Real World Uses of Graphs
07:08 Graph Terminology – Neighbors and Adjacency
08:32 Edges Incident on Nodes
09:20 Graph Representations – Edge List
09:59 Adjacency List
10:27 Adjacency Matrix
11:19 Directed Graphs
13:04 Weighted Graphs and Path Costs
15:24 Video Conclusion

=-=-=-=-=-=-=-=-=

Thanks for watching!

Find us on other social media here:

• https://www.NeuralLantern.com/social
• Twitter / X: https://x.com/NeuralLantern
• Rumble: https://rumble.com/c/c-3696939
• BitChute: https://www.bitchute.com/channel/pg1Pvv5dN4Gt
• Daily Motion: https://www.dailymotion.com/neurallantern
• Minds: https://www.minds.com/neurallantern/
• Odysee: https://odysee.com/@NeuralLantern:5

Please show your support!

• Buy me a coffee: https://ko-fi.com/neurallantern
• Subscribe + Sharing on Social Media
• Leave a comment or suggestion
• Subscribe to the Blog: https://www.NeuralLantern.com
• Watch the main “pinned” video of this channel for offers and extras

Hello there. Let’s talk about graphs in the context of data structures and computer science.

I just want to talk to you about some of the basics of graphs, some ways that we could

implement them in the future, and some terminology. Okay, so for starters, we have a little

For starters, we have a little blank graph sheet here.

If you saw my previous video, you’ll know already that this is a valid graph.

It’s just totally empty.

There’s nothing on it.

But let me draw some data in this graph.

So graphs are collections of nodes and edges, or vertices and edges, or vertex and edges.

The nodes themselves, they are custom classes sometimes, other times not.

But you can imagine that they hold some sort of custom data.

of custom data so i know i did this in my last video but i just want to emphasize that this graph

class if we’re talking about c plus plus it should be a template class meaning we can specify a

custom data type that the nodes will hold and also a custom data type that the edges will have as

their weight you know typically when you see examples of this in the wild it’s just going to

floats and strings exotic custom classes depending on your use case it may or may not be useful to do

that but so we’ll have a data type for our nodes and i’ll call it like n type for like our node

type and then we’ll do another one called e type for edge type i don’t know if that’s the best way

to write those but i’m just going to do it anyway imagine that your glass your graph like we said

So I’m going to put a node class here.

You can imagine this as a vertex class.

And I’m going to say that this node holds an n type data.

And we’ll just call it data or node value or whatever you want.

And then the same thing for the edges.

We’ll say we have an edge class.

I think in my last video, instead of doing a node class, I did a vertex class.

It’s kind of all the same.

We’ll say we have an e type and we’ll call it weight or value or data if you want.

or value or data if you want but I think weight is a little bit closer to what we’re going to

actually be doing with it and what do I mean by n type and e type like what are those data types

there that just means these are placeholder tokens so when the user actually uses your graph by

making an instance of your graph class like they create an actual graph off of your blueprint

class here they might decide that they want integers inside of their nodes so that’s what

They might decide that they want floats inside of your nodes, inside of their nodes, or some

other data type.

And so that means like at runtime or at, I think actually at compile time for C++, this

end type would actually change to int if they chose to use integers on the inside.

Same thing would happen for the edge, whatever they choose for the E-type token is just going

to end up being used at compile time to replace that E-type.

So I don’t know.

Here’s an example.

example, I got a fly in my room, it’s bothering me. Imagine the user says I want a graph.

And I’ll call it G. And so they just have to kind of specify the two data types, maybe they want the

graph to have integer values in the nodes. And maybe, you know, floating point double precision

floating point values on the edges. In terms of weights, you know, you could do something like

And we have edges and this graph right here is valid.

It’s just one node kind of floating around by itself.

This graph is also still valid, even though we have two nodes that are floating unconnected

and also with the same value.

I’m just going to change the value to be different.

Maybe I’ll get rid of this extra thing here.

So this is a valid graph still.

We could have like a whole bunch of nodes all over the place and they don’t really have

to be connected.

This is still a valid graph.

change this to like a three, maybe change this to like an 11, change that to a six.

What else can I change?

How about like a 13?

How about like a 17?

Are there any duplicates?

I don’t think I see any.

All right.

So this is a valid graph.

The next thing that we could add to our graph is edges.

So edges are, you know, little mini data structures that connect nodes.

In this particular graph, I’m choosing to not have direction on my edges, which means this is a special type of graph.

Or four that we talked about in the previous video.

This is unweighted and also undirected, meaning there’s no weight assigned to the edges,

which means that template weight value or the weight data type that we just talked about before.

It’s kind of useless for this particular graph because I’m saying it’s unweighted.

well uh all the edges if we wanted to travel through the graph along the edges we could just

sort of go in any direction we felt like so this is unweighted and undirected

um let’s see what else can i show you real fast okay so let’s talk about um well really fast let’s

talk about the uses that you can have for a graph i think i talked about this in the last video

but um you know what can we use graphs for some people think they’re databases they’re not really

They’re not really databases.

You could technically do that, but it would be pretty slow.

There are much better data structures for databases.

Really what graphs are mostly used for is to represent relationships between different

things.

I think I said this in the last video.

Imagine if every single node that you see here is a city and the edges represent flight

paths.

So we could fly between city seven and 11.

Oh, that’s funny.

I’m hungry for candy bar now.

between city seven and 11 and back and you know back in the other direction if we want to but we

can’t actually fly from city seven to six because there’s no edge there so we could represent

computer networks we could represent road maps airports dependency graphs game maps you could

say like every node is somewhere your character could stand and an edge represents where your

or represents a connection to another node so that you know your character could move there

there’s all sorts of different things that you could represent with the graph but

it’s not necessarily a fast database it’s more of like a relationship

not to be confused with relational database which is supposed to be lightning fast

like if i wanted to search for the number 17 in this graph it’s not going to be log time like a

proper database should be it’s not going to be constant time like a hash table based database

or like a no sql or whatever um so we have undirected and unweighted uh we talked about

like different uses let’s talk a little bit about terminology okay for starters notice how there’s

no hierarchy in this graph in other videos we’re going to talk about binary search trees and we

have to have like a hierarchy there’s no parent there’s no child in these graphs there’s no uh

you know like grandchildren ancestors descendants because there’s not really like a hierarchy it’s

It’s just things are connected to each other or they’re not.

But we can have something called neighbors.

For example, if you can reach a node in one hop, then you might be able to call that a neighbor.

So 6 and 17, those are neighbors.

Maybe I’ll just type neighbors right here.

Oops, neighbors.

Because we can reach them in one hop.

Later on, or especially if I don’t remember to mention this,

to our graph, then something is only considered a neighbor if you can reach it while respecting

the direction of the graph. So we have like neighbors as 6 and 17. So that means 6 and 11

are also neighbors. 6 and 12, not neighbors because they can’t reach each other in one hop.

Let’s see. Adjacency is basically the same thing. I can’t remember. I think we use adjacency more

often in directed graphs, but we could say that 6 and 17 are adjacent to each other,

adjacent to each other, which is in this context, sort of a synonym for neighbors.

Okay. Something else that I want to talk about in terms of edges,

edges are considered to be incident upon nodes or vertices. So like, you know,

if I have an arrow that just kind of points to these two things, I could say,

you know, edge is incident upon three and 12. It’s just, it just means,

and 12th. Okay, what else should we talk about? We should talk about connected versus, no,

that’s another video. Okay, I’m going to do another video for connected versus not connected graphs.

Maybe I should mention that there are three ways that we can represent a graph, and then maybe I’ll

upgrade to a directed graph in a second. If you want to know about the four different types of

graphs, see my previous video. But for now, I’m going to say there are three ways we could

to represent these graphs. The first way, and I’m talking about how can you represent these

graphs inside of the machine? Like how can your computer store and process this graph and maybe

run algorithms on it? So the first way that we could represent, at least that I’m going to talk

about, is an edge list. Edge lists are super simple. I’m going to do a dedicated video just

for edge lists in the future. They’re not very fast, but they’re very easy to implement. So

So honestly, if you’re just starting with this stuff, I would recommend just implementing an edge list first

The next thing that you can do to represent a graph in the machine is make an adjacency list

Adjacency lists are just a little bit more complicated

But they’re typically faster than edge lists. Not always not in all cases and

In terms of time complexity, you might not feel like you notice much of a difference

but empirically

the option of skipping a lot of examinations when you don’t need to examine something,

you kind of skip it.

We’ll talk more about that in the future.

But we have an edge list and adjacency list of representation.

And then we have an adjacency matrix.

I wish I had spell check on this.

Otherwise, this is going to be humiliating.

An adjacency matrix is sometimes a lightning fast representation of a graph.

At first, you might think, wow, that’s amazing.

I’m always going to use that.

always going to use that. But all of these representations have strengths and weaknesses.

None of them are better than the others in every single circumstance. So, you know, computer science

and data structures, it’s all about weighing the pros and cons and picking the right representation

or algorithm or whatever that’s best for you and the code and the data that you’re actually going

to run. So three different ways that we can represent a graph in the future. And let’s see,

already on this. We talked about the basic ways to use them sort of. We talked about neighbors

and adjacency. Oh, I got to upgrade to a directed graph real fast just to kind of show you the

difference here. Okay, so I’m going to duplicate this and I’m just going to start adding direction

to all my edges. In my previous video, we talked about this. If you add direction to even one edge,

then you have to add direction to all the other edges. Otherwise, you will have an invalid graph.

graph so notice how I add a direction to one edge I now have an invalid graph so

I’m just gonna do this change every single edge so that every single edge

has a direction you know the basic thing we kind of talked about this in my

previous video is that when traveling through the graph you’re supposed to

only be able to travel in the direction of an edge which means if you look at

this thing right now you’re supposed to be able to go from 11 to 7 but you’re

be able to go from 7 to 11 because that violates the direction of the edge. When we add direction

we’re sort of like reducing you know the flexibility of the graph so you can imagine

that the previous version that was undirected it was sort of like every single edge here

was really two edges pointing in opposite directions if that makes sense. So if you

wanted to make sure that you could go back and forth between edge sorry between node 7 and 11

the opposite direction you can also do things called parallel edges which is just to say

i’m going to add multiple edges that that go in the same direction from the same start node to

the same end node but i’m not going to do that here that makes it more complicated for some

representations but we can just sort of add a whole bunch of edges i’m just going to say one

going back and forth there and so forth remember in my previous video we talked about weighted edges

about weighted edges which means we could add a cost to traveling along an edge so you could say

something like uh i don’t know going from 7 to 12 let’s add another edge here if there was a cost

on all these weights maybe i should just add that for fun we could maybe calculate which path would

be better so let’s say we got ones over here and we got fives over here um and maybe like a like

and I’m going to do like an eight.

By the way, these sixes don’t have to be the same.

You could just be two different numbers.

So I’m going to do like a three here.

And let me just see, have I added a weight to every single edge?

So I know I did this in the previous video,

but I want to do it again real fast.

If we chose to take a path from seven to 12,

and we said seven to 11, and then 11 to 12,

that’s a very specific path, which is,

it’s going to cost us five to go along that first,

as you have to go along that first edge and then the second edge is going to cost us six

and we’re only traveling along two edges so the total cost of that path is 11.

On the other hand let me actually make this look pink.

On the other hand if we’re taking a different path we might come up with a different cost

depending on the graph. So let’s say we start at 11 start at 7 maybe we want to go down to 3

to three and then from three we’ll go to 12 well that might be a different cost so i’m going to say

the cost of this particular path is traveling it’s going to cost us one to go down that first edge

and then a two to go down that second edge which means the total cost of getting to 12 is only 3

if we take that orange path versus 11 if we take that pink path i hope you’re starting to visualize

how graphs might be useful to visualize costs if this is a network map we just figured out that

network map we just figured out that one route through the network might be faster or less

costly than the other or if this is like an airport map maybe you do want to take you know

that layover that goes down south instead of that layover that goes east in terms of

i don’t know frequent fire miles that it costs you or money it costs you or jet fuel that it

That’s all I wanted to talk about in this video.

I’m going to make one more video today.

Well, it’ll be released.

I don’t know when, but like in my present moment.

I’m going to make another video right after this

where we just talk about connected graphs versus not connected graphs.

Thank you so much for watching this video.

I hope you learned a little bit of stuff and had a little bit of fun.

See you in the future.

Okay.

In the future.

in the future.

So we’ll be able to do more videos, longer videos, better videos, or just I’ll be able to keep making videos in general.

So please do me a kindness and subscribe.

You know, sometimes I’m sleeping in the middle of the night and I just wake up because I know somebody subscribed or followed.

It just wakes me up and I get filled with joy.

That’s exactly what happens every single time.

So you could do it as a nice favor to me or you could troll me if you want to just wake me up in the middle of the night.

Just subscribe and then I’ll just wake up.

I promise that’s what will happen.

happen also if you look at the middle of the screen right now you should see a QR code which

you can scan in order to go to the website which I think is also named somewhere at the bottom of

this video and it’ll take you to my main website where you can just kind of like see all the videos

I published and the services and tutorials and things that I offer and all that good stuff and

if you have a suggestion for clarifications or errata or just future videos that you want to

videos that you want to see please leave a comment or if you just want to say hey what’s up what’s

going on you know just send me a comment whatever i also wake up for those in the middle of the

night i get i wake up in a cold sweat and i’m like it would really it really mean the world to me i

would really appreciate it so again thank you so much for watching this video and um enjoy the cool

so

Thank you.

The post Graph Basics in Data Structures: Nodes, Edges, and Representations appeared first on NeuralLantern.com.

In this video we break down the four main types of graphs used in computer science: undirected unweighted, undirected weighted, directed unweighted, and directed weighted.

We start with the basic idea of graphs – collections of nodes (vertices) and edges – and then explore each type with clear examples. Learn how these graphs represent real-world relationships like computer networks, airport routes, road maps, and game maps.

Perfect for anyone learning data structures, algorithms, or preparing for coding interviews.

00:00 Introduction to Graphs
00:19 Basic Graph Definition
00:48 Nodes and Vertices
01:01 Empty Graph Example
01:17 Graph Implementation Concepts
02:02 Node Data and Templates
03:22 Adding Nodes
04:00 Adding Edges
04:44 What Graphs Represent
05:36 Graph Use Cases
06:56 Real-World Examples
08:35 Four Types of Graphs
08:52 Undirected Unweighted Graph
10:40 Unweighted as Unit Weights
11:40 Undirected Weighted Graph
13:32 Weighted Graph Benefits
15:52 Directed Weighted Graph
19:50 Directed Unweighted Graph
20:32 Summary of Four Graph Types
21:19 Closing and Future Videos

=-=-=-=-=-=-=-=-=

Thanks for watching!

Find us on other social media here:

• https://www.NeuralLantern.com/social
• Twitter / X: https://x.com/NeuralLantern
• Rumble: https://rumble.com/c/c-3696939
• BitChute: https://www.bitchute.com/channel/pg1Pvv5dN4Gt
• Daily Motion: https://www.dailymotion.com/neurallantern
• Minds: https://www.minds.com/neurallantern/
• Odysee: https://odysee.com/@NeuralLantern:5

Please show your support!

• Buy me a coffee: https://ko-fi.com/neurallantern
• Subscribe + Sharing on Social Media
• Leave a comment or suggestion
• Subscribe to the Blog: https://www.NeuralLantern.com
• Watch the main “pinned” video of this channel for offers and extras

Hello there! Let’s talk about four different types of graphs that you can use and how they relate to computer science.

Okay, so you can see like I’ve got like a blank little graph paper up here.

I’m going to talk about graphs and just the very basic idea of graphs in general

and then show you the four different types of graphs that we have.

about how to implement graphs inside the machine, time complexities, maybe graph algorithms,

and a whole bunch of stuff, terminology, everything. Okay, so the first thing is, I guess I’m going to

assume probably most of you have sort of seen a graph before and you kind of understand a little

bit about it already, but I’ll say that a graph is basically a collection of nodes, also known as

vertices or vertexes, and edges, which are the lines that connect nodes to each other. This screen

See, this is a valid graph.

I’m not talking about the graphing paper.

It’s just an empty graph.

There’s nothing there.

So it’s still valid.

It’s just blank.

Okay, so then what I want to do is start drawing some nodes.

What are the nodes again?

Those are just vertices.

Those are just like little data structure objects you can imagine in the code.

I don’t want to get too far ahead of myself, but imagine that you have a class called graph.

This is just one way to imagine.

We have a class called graph and then a nested class inside of a graph called a node or a vertex

If you want to be more fancy

So the vertex class itself by the way

This is not always going to be the way that you actually do this in your code the other representations that we’ll talk about sooner a little bit easier, but

The vertex class itself needs to basically hold some data

Depending on your implementation it might know about who it’s connected to maybe the graph knows that instead

instead. In my implementations, the graph is going to know everything, but the vertex or the node

itself needs to hold one piece of data. That’s kind of the whole point. So I’m going to say that

the data type that these nodes hold are just integers. So I’m just going to put like a six in

here just to indicate we have one node and the templated data type that it holds is an integer.

And the specific integer for this specific node is just the number six. You can have any template

any template type if you really want to you can people put floats in there you could put a custom

custom class in there whatever you want but i just want to show you that we have a class called

vertex or node and inside of it’s got a template type maybe just to make this a little bit more

clear i’ll say you can imagine inside the vertex class uh there is a template type and we’ll call

it uh i don’t know node node value type or something and we’ll call it data and then up

I’m doing C++ up here.

We have to kind of define the whole graph class as a template class.

Now, of course, you could define the vertex class as the template class,

but if you define the graph class as a template, then it all kind of falls through.

So I’m just going to say class node value type.

And so if you’ve written template classes before in C++,

now you know that the user can instance the graph and at the same time,

specify what is the data type of the stuff that the nodes hold.

the stuff that the nodes hold.

We do the same thing for edges too,

but notice how there are no nodes that are connected to each other.

So we have no edges in this graph.

This is still a valid graph,

but we could just sort of copy a node just for fun and say,

all right, we’ve got two nodes now, two vertices.

They could have the same value if you want.

Graphs are supposed to, you know, support duplicate values in the nodes,

but I’m just going to change the value here.

This is also a valid graph.

You don’t really need edges to have a valid graph.

edges to have a valid graph. This is just something called a something called a graph that is not

connected. We’ll talk about all that terminology and how to detect it in a future video. For now,

I’m just going to say we have like a little graph here, which is kind of boring, but I’m going to

add an edge. An edge is basically just, you know, a little mini data structure that connects two

nodes. Depending on the way you represent this in the machine, which we’ll talk about in future

well, a whole bunch of different ways.

You could imagine this as a full-fledged class,

although that’s not always going to be the way that we represent an actual edge.

So imagine that we have a nested class called edge.

And inside the edge class, we’ve got, you know, some stuff.

We could have a weight, which means the cost of traveling against the edge.

We could have many other properties.

For now, I’ll just try to keep it simple.

is pretty much a collection of vertices and edges and some sort of connection.

What is a graph really for?

Some people at first think that a graph is another way to represent a database.

I’m going to erase this thing over here.

Graphs, you could sort of use them as databases,

but they’re not very good as databases because

it would be really, really slow to search through the graph

to find some piece of data that you’re looking for.

It could be like a linear time database.

better would be to take this graph and add a bunch of rules as you probably have found

in my other videos by now and turn it into a binary search tree.

A binary search tree is lightning fast.

It runs in log time.

Hash tables are faster than binary search trees, but basically a graph is always going

to be way slower than a binary search tree unless the binary search tree is severely

imbalanced.

But that’s something for another video.

Anyway, so we have a graph and it’s not a good database.

What would a graph be good for?

would a graph be good for? Well, graphs are usually pretty good to help you represent

relationships between things. For example, the six and the one, imagine the six is something,

maybe it’s a computer, maybe it’s a city, maybe it’s, I don’t know, like a train station,

and the edges could represent connections. So I’m just going to start changing these values

have some nodes just kind of hanging out off to the side, not really connected to anything.

Maybe not great for your particular use case, but like it’s a valid graph. So I’m just going to,

I’m just going to connect this and try to make this into a better graph.

That’s a little bit more interesting. So we’ve got graphs that do a whole bunch of different

things. Let me change these values real fast. I’ll maybe turn that into a 13 and turn that

So imagine that we have like a little connection here, a little connection here, maybe another

connection here and another one there.

And you know, you are allowed to have connections that sort of look weird, like going from this

six all the way around to this 13.

That’s totally valid also.

So I’ve basically just drawn a random graph, random nodes and random edges.

Imagine that every single node here is a computer in a computer network and imagine every edge

every edge which connects the nodes is just some sort of a connection let’s say a network cable

or a wi-fi signal or something like that so if you imagine it that way then this graph could

represent a network topology a bunch of computers connected together if these were cities and this

is like actually maybe these are airports in cities you could imagine a graph could represent

the relationship between different airports in which planes will fly notice on this graph just

that the uh you know the uh the city number one uh there are no flights connecting it directly to

city 44 but you could probably imagine well if we take a flight to uh from city one to city 10 and

then from city 10 to 44 then we can get from one to 44 we just have to be clever about our connecting

flights um let’s see so we could do like road maps airport maps the worldwide web is basically a graph

at least from a certain perspective electrical circuits that are connected to each other

are connected to each other even game maps what if your character is allowed to stand here in

in space number three on some map and the character is only allowed to travel to space 13 or

space 6 but not directly to space 1 well it could be a map that helps you understand where your

character can go in a game okay so that’s like the basic idea of of what a graph is and uh how it

actual four types of graphs that I’m going to go over in more detail in future videos. Let’s see,

what time is it right now? We got like 10 minutes. Okay, so I can still kind of make this fast.

So the first type of graph that we’re looking at right now is actually something called an

undirected, unweighted graph. Why is it, let’s see, let me write this down first. It’s an undirected,

undirected, unweighted graph. So why is this undirected? Because the edges don’t have direction.

If I was standing in, you know, city six and I wanted to like drive or fly or whatever

from city six to city three, then I should be able to do it because this edge that connects

them doesn’t really say that I have to go in one direction or the other. I could also go to city

three and then just walk right back or fly right back to city six. There’s no direction. So there’s

no direction. So there’s an this that’s that’s why this is an undirected graph. This is an

unweighted graph because we haven’t specified a cost for traveling along an edge. For example,

if you know, if you’re at city three here, and you want to fly to city 13, how much jet fuel

does it cost? How much time does it cost? If three is a computer and 13 is a computer,

and the edges like a network cable, like how much money does it cost to transmit the data?

transmit the data or what is the lag in milliseconds.

You know, you can represent all sorts of things with these edges,

but there’s no value on these edges,

which means there are no weights to these edges.

So that’s why this is an undirected and also unweighted graph.

Uh, the first upgrade that I want to do is just kind of show you what you can

sort of assume about an unweighted graph. This is not always true.

It just depends on who you talk to and what your application implementations are.

So imagine the node that goes from six, sorry, the edge that goes from six to one.

If it’s an unweighted graph, you could just probably imagine that every weight is just a one.

The point being that it always costs the same amount to travel along every edge,

because in an unweighted graph, we don’t differentiate between the different edges

in terms of their costs.

We could just put a bunch of ones on all these edges.

And it would still, you know, basically be considered an unweighted graph.

It depends on who you talk to.

maybe all the weights are zero, maybe all the weights are 10 or whatever.

But, you know, usually I put a one there because I’d like to imagine the cost could just be the number of hops.

So, for example, if I wanted to go from city six to city 10,

I could probably, you know, start at city six and then go to city one and then hop to city 10.

How many actual hops did I do? I did two.

I could also come up with that number by just looking at the sum of all the weights of all the edges.

all the edges. So notice how when I go from six to one, that costs me one weight or one hop. And

then when I go from one to 10, that’s another one. So if you put ones on all the edges in an

unweighted graph, then you’re kind of saying the total cost of some path is really just the number

of hops. So it’s up to you. Anyway, that’s unweighted and undirected. Let’s upgrade this

see we have an undirected and unweighted and i’m just going to duplicate this real fast and change

this to a weighted graph so undirected but also weighted and the thing is as soon as you start

putting numbers on a graph on the edges of a graph well then it’s considered weighted so even even a

graph that has all ones on all the edges you could also call that weighted but now you have the

freedom since it is considered a weighted graph to just assign different values to all the edges

to all the edges. Again, these edges are a class sometimes, or you can think of them that way

inside the graph. And the edge weights themselves are definitely considered a T type, a templated

type, which means, you know, right now I’m clearly typing integers, but you could type some other

data type. You could type floats. You could type some weird data type, like a string.

Whether or not that’s going to be useful depends on your program, you know, what you’re trying to

you know, what you’re trying to do with the graph. But let’s see, I think I’ve added custom numbers

to every single edge. So now this is definitely an undirected, but weighted graph. That’s the

second type of graph that we’re talking about. Okay, what’s what’s cool about a weighted graph?

Well, imagine again, that this is an airport map, where we’re representing relationships between,

you know, cities, like where can we fly and stuff. We’re basically saying at this point,

it’s going to cost you 44 of something.

Maybe this is a graph representing jet fuel or time or frequent flyer points or something like that.

If you consider your edges to be custom classes,

you could even put a whole bunch of different types of values in your graph at the same time

to make it a little bit more flexible.

But for now, we’ll just say there’s one templated type,

which means if we go back up to this code real fast, where was that code at?

Where was that code at?

And we had, you know, our rough idea of, you know, what the, what the graph holds, you

know, it holds like vertices and edges.

We could upgrade this just a little bit to say that there is a, an edge value type.

So I’m going to say class edge value, edge weight type, something like that.

for the edge so that I can save characters. And then here, I’ll change this to a type for the

node. This is why we call it T type. There’s like, we put the keyword template here in C++.

And then sometimes people just use T’s here for these tokens. So I’m just going to say

the type of data that a node can hold is going to be the T node. And then the type of data that

the edge could hold would be the T edge. We’ll call that data. Or we could call that weight,

because usually that data comes into play when you’re traveling along an edge, right? So there’s

traveling along an edge, right? So there’s like two different types here. Anyway, so we got an

undirected and unweighted graph. If we traveled from city six to city one, that costs us 44. But

if you look at the graph a little bit more closely, we could take the longer way around. We could say

go from six to three, and then go from three to 13. And then actually, let me change the color

to orange so that you can see there’s different paths, six to three, and then three to 13,

and then 13 to one, even though we took more hops,

and that might have been considered more expensive

in an unweighted graph,

you can see that the cost of the first path

from six to one, that’s 44.

And the cost of the second path is seven plus three,

that’s 10, and then plus nine, so that’s 19.

So if we take the long way,

it actually costs us less

of whatever we’ve determined this unit is.

You know, less jet fuel, less time, less whatever.

less whatever these graphs in the machine are not necessarily going to be to scale because the

machine in your computer your computer doesn’t really keep track of like the physical positioning

of all these nodes and edges it just can keeps track of the relationship between the nodes and

the edges and the weights and all that stuff so two different paths that we could take to get

from six to one one of the paths is less expensive um or less time costly or just whatever and a graph

data structure can kind of help us figure that out if we’re using an algorithm that understands

weights okay so undirected and unweighted let’s add direction so um i’m going to erase this stuff

right here real quick and in an undirected graph remember you can just kind of go in either

direction along any edge but in a directed graph every single edge needs to have a direction so as

I change one of the edges to have direction, then I must change all of the edges to have direction

as well. So I’m just saying, okay, as soon as I did that, now this is an invalid graph

because some of the edges don’t have direction. So now I need to fix everything. So I just,

I’m going to arbitrarily and randomly choose a direction for every single edge like this.

And then as soon as I’m done, I’m going to deal, I guess, with that giant edge

that giant edge. So I’m going to go like that. So let’s see, all the edges seem to have direction.

Now I’m just going to hand draw an arrow on one side of this giant edge. Okay. So this is directed

and also weighted. What can we do with the directed graph? Well, it just basically tells

you which direction you’re allowed to travel in. What if you have an airport where city six can

only fly to city one, but city one, for some reason, never flies to city six. You got to take

take like the long way you got to go from city one to 13 to three to six that’s something that

a graph could help you represent what if your character in your game can only go in one direction

but not the other direction okay no problem i mean that’s pretty much it you’re only allowed

to travel in the same direction as the edge points but now we have a graph that is a lot less

flexible because for example before we used to be able to go from city uh 10 to city 44 and then

then come back again later if we wanted in the opposite direction. We can no longer do that

because this edge only goes to 10. It doesn’t even go to 44. We can’t even ever actually get to 44.

How do you sort of solve that? Well, just add another edge in the opposite direction.

In graphs, you are allowed to do something called a parallel edge,

which just basically means, you know, two edges between the same pair of nodes that just point

in the same direction. You’re also allowed to do, you know, opposite facing edges. So

edges so i just added a second edge there going from 10 to 44 and now if i was you know hanging

out in city 10 i could just go back and forth between city 10 and 44 as much as i wanted to

oh i forgot to add an edge weight for that new edge which means i wrote down an invalid graph

so i’m just going to say two so uh maybe the wind is blowing in in your favor when you’re going from

city 10 to city 44 maybe it’s blowing against you if you’re talking about city 44 to city 10 you

you know whatever but you just have to have edge uh edge weight on every single edge

okay so uh that’s directed and also weighted um and you can probably imagine previously when we

had an undirected um graph when there was just like you know one edge going between uh two nodes

and there was no direction on it like you know 44 to 10 if we just had like one edge with no

have two edges each going in the opposite direction so we have directed and weighted i think the last

thing that we didn’t do was directed and unweighted right so we have let me just double check real

fast here we have undirected and unweighted and then we had undirected and weighted and then

directed and weighted okay so now let’s do um i’m getting lost already oh my gosh i can’t believe i

I saw undirected and unweighted so we did undirected twice already undirected so we’re

going to do directed and unweighted next okay so the next graph a little bit less useful than

what we’re looking at this this type of graph is a little bit more useful we’re going to do

directed and unweighted oh my god okay directed and unweighted so directed and unweighted you

Directed and unweighted, you can imagine, just means we get rid of all these weights.

And then we keep the direction on all the edges.

So this means we can keep track of where we’re allowed to go, if we’re pathfinding or just whatever.

But we don’t really know what it costs to travel between the different graphs.

So that’s directed and unweighted.

Let’s see here.

I’m going to just duplicate this or just make a new blank slide.

Okay, undirected, oh gosh, I’ve got pink letters.

Let’s see, undirected plus unweighted.

And we’ve got undirected plus weighted.

And then we’ve got directed plus unweighted.

I don’t think I’m writing these down in the same order,

but that’s okay.

And then we’ve got directed plus weighted.

So basically, you know, four types of graphs

that we can talk about.

In future videos, we’re going to go over graphs

in more detail.

We’ll talk about graph terminology,

maybe some pathfinding algorithms.

And yeah, so this is just a basic intro.

How much time do we spend already?

Oh God, we spent so much time.

Spent like 22 minutes.

Dang, man, even the smallest thing takes time.

So I’ll see you in a future video

when we talk more and more and more about graphs

and other data structures concepts.

Thanks for watching this video.

I hope you learned a little bit of stuff

I hope you learned a little bit of stuff and had a little bit of fun.

I’m out of here.

Go.

Hey, everybody.

Thanks for watching this video again from the bottom of my heart.

I really appreciate it.

I do hope you did learn something and have some fun.

If you could do me a please, a small little favor,

could you please subscribe and follow this channel or these videos

or whatever it is you do on the current social media website that you’re looking at right now,

it would really mean the world to me.

And it’ll help make more videos and grow this community.

So we’ll be able to do more videos, longer videos, better videos,

or just I’ll be able to keep making videos in general.

So please do me a kindness and subscribe.

You know, sometimes I’m sleeping in the middle of the night

and I just wake up because I know somebody subscribed or followed.

It just wakes me up and I get filled with joy.

That’s exactly what happens every single time.

So you could do it as a nice favor to me or you could you control me if you want to just wake me up in the middle

And I just subscribe and then I’ll just wake up. I promise that’s what will happen

Also, if you look at the middle of the screen right now

You should see a QR code which you can scan in order to go to the website

which I think is also named somewhere at the bottom of this video and

It’ll take you to my main website where you can just kind of like see all the videos

I published and the services and tutorials and things that I offer and all that good stuff and

and if you have a suggestion for clarifications or errata or just future

videos that you want to see please leave a comment or if you just want to say hey

what’s up what’s going on you know just send me a comment whatever I also wake

up for those in the middle of the night I get I wake up in a cold sweat I’m like

it would really it really mean the world to me I would really appreciate it so

enjoy the cool music as as I fade into the darkness which is coming for us all.

Thank you.

I’m going to go ahead and get started.

Thank you.

Hello there.

Let’s talk about the four types of…

Hello there.

The post 4 Graph Types: Undirected vs Directed, Weighted vs Unweighted appeared first on NeuralLantern.com.