Let's have a standard topological ordering algorithm (from CLRS):

Topological_ordering(G)
    foreach vertex v in V do
        v.color = white
    
    for each vertex v in V do
        if v.color = white then
            Stack = DFS(G, v, Stack)
    return Stack

// DFS

DFS (G, v, Stack)
    v.color = gray
    for each u adjacent of v do
        if u.color = white then
            Stack = DFS(G, u, Stack)
    v.color = black
    Stack.push(v)
    return stack

Now let's apply this to a cyclic graph G.

We will not have a topological ordering of the vertices of G, but we shall have a topological ordering of the graph of the Strongly Connected Components

>The graph of the Strongly Connnected Components derived from the graph G is a graph in which each SCC is represented by only one vertex (also called compressed SCC graph

Example

For example let's look at this graph: https://imgur.com/a/0EXOxJt (sorry for the poor drawing skills). In green the SSC of this graph.

Applying the algorithm above, one possible stack configuration is:

head ----> 2 ; 3 ; 4 ; 5 ; 1 ; 6 , 8 ; 7 ; 9

As you can see the elements of an SCC are "all together". How to prove this mathematically? Thank you.

Just a quick question due to the fact off me being pretty nee to CCW. Why does CCW not like any white in images made as .png? Also why doesn't it show the transparency?

So I'm just starting to dabble in CCW and the micro800 series. Not entirely sure how I feel about it. So features are nice..... so not so much. One issue I've been having for days is getting my analog outputs to take my 4-20ma singal. I'm using the OF4 analog output extension.Is there anything special I need to do? Any scaling, or initiating?

Howdy all

I bought this asrock x399 fatal1ty motherboard off someone on offerup, however as soon as I pressed the power button the board started smoking. After doing a quick visual on the board it appears they failed to tell me that an SMD on the back of the board was broken off the board (it didn't look "blown" but I don't really know what I'm looking at). was just labelled R10 and I have been unsuccessful in finding what part it could be, as I haven't gotten any real matches. The closest I've gotten is finding a 250mW current sensing resistor (RL1220S-R10-F) but it didn't look the same. The smoke seemed to be coming from the same side as the broken part so I'd wager that it was causing the issue but if anyone else has any thoughts I'm all ears.

Here's a photo of the board and how it was originally attached.

I tried contacting the seller on offerup but they basically told me to pound sand. If anyone here knows anything about this I'd be forever in your debt if I'd be able to find the component and solder it back on. Also on a somewhat related note, one side seemed to have two metal leads coming out of it and the other side only had one, but on the mobo itself both sides seemed to have only one contact.

Can basins merge together in a larger basin?

Edit: I just need to read. The answer is NO.

I know that there are some regulation that imposes limitation for the THD.

Besides that, what motivation can you give to the necessity of harmonic reduction?

Are some kind of load sensible to harmonics? How is the reliability of the equipment affected?

So the definition of homotopy doesn't prevent the deformation from making the curve intersect itself this can cause the creation of additional regions or regions to disappear what should I use instead?

video link : https://youtu.be/bBpMphhS5Ug

i apologise if this question is not directly related to motors, but i cant seem to find a more suitable subreddit to ask this question.

i am working on this vending machine ( video link attached above ) for my school project, but i can't seem to figure out what was the yellow thing ( that looks like a pushpin ) that was used in here, 1:48 of the video. it was attached to a spoke.

https://preview.redd.it/gwrzgs20q1081.jpg?width=564&format=pjpg&auto=webp&s=2a41b1428259590a192033a8675cc3123e6fce55

the components needed for the machine was stated in the description of the video here. but the yellow thing wasn't ( directly ) mentioned. i assumed it was a spoke head and went ahead and bought two of them.

supposedly, the yellow thing has a hole on the top to fit into the drive shaft of the dc motor gearbox. heres a picture of it. but the holes on the spoke heads i bought were too small to fit, and the shape looks really different from the one used in the video. i'm not sure if i'm supposed to get a bigger size for the spoke heads, or is the yellow thing not related to spoke heads / mechanical / electronics at all?

below are a list of components that could possibly be what was used :

1. spoke heads
2. wheels for dc motors ( i'm not sure what it's called ) it seems to fit the drive shafts of dc motors perfectly.
3. push pins ( quite unlikely )

-

any advices / helps would be highly appreciated. thanks!

This is version 13, by the way. And I came up with this list in literally less than 5 minutes. I also limited it to features C-More has but PV800 doesn't.

1. Full Developer edition isn't free (unlike C-More, Maple Systems)
2. Whenever I click a new object, the properties pane scrolls to the end, so I have to scroll all the way back up to the top to set tag bindings, etc.
3. Tag bindings don't allow you to just type/Ctrl+V a tag name in the field and have it auto complete. You have to click the down arrow first, then type a tag name, and then the shitty filtering that doesn't use wildcards will start working.
4. The numeric entry object has a display value and a separate binding for it, that does work in runtime, but not in development mode. So you can't see how your numeric display on your entry object will look until after you compile, download, and run your application live.
5. The editor isn't true WYSIWYG. Oftentimes text will look totally fine in the development environment but live on the terminal it will be cut off or abbreviated.
6. Lets you do things that will cause a validation fail (add too many tags, leave a tag without an external address reference) without warning you.
7. No object grouping.
8. Visible property binding is one-way boolean only. You can't bind to an analog value. You can't even invert the binding so that the visibility is false when the tag is true. You have to create a separate inverted tag in the ladder logic.
9. Lets you delete tags that are being used in the application without even warning you.
10. Ramp buttons require a weird Numeric Increment/Decrement object that isn't very intuitive to set up.

I know how to find out connected components in a graph in O(V + E), but I was thinking what if there are q queries that can add or remove edges. Then our overall complexity would become O(q(V + E)), is there a better way of approaching this problem or do we have to make a DFS call to update our connected components every time?

I don't understand why the stack in this algorithm is needed. there is a stack which you do DFS and insert all vertices when they finish to the stack.
instead of a stack why not do a for loop over all vertices and do DFS if they are not visited?
why the algorithm is not like that:

1. Reverse all the edges
2. for loop over all vertices {
   if vertex is not visited then {
   print "new strongly connected component:"
   DFS(vertex)
   }
   }

Before installing the soft mod, I had my OG Xbox connected to an RCA V-Port television using the V-Port cable, which is essentially a repackaged component cable. This gave me significantly better visuals than the standard composite cable.

With the soft mod installed, the v-port signal dies as the soft mod dashboard launches. Is there any way I can solve this problem by changing some settings, or am I stuck with composite video on this CRT?

Feeling very lost.

How does cutting any edge increases the number of connected components really

Howdy all

I bought this asrock x399 fatal1ty motherboard off someone on offerup, however as soon as I pressed the power button the board started smoking. After doing a quick visual on the board it appears they failed to tell me that an SMD on the back of the board was broken off the board (it didn't look "blown" but I don't really know what I'm looking at). was just labelled R10 and I have been unsuccessful in finding what part it could be, as I haven't gotten any real matches. The closest I've gotten is finding a 250mW current sensing resistor (RL1220S-R10-F) but it didn't look the same. The smoke seemed to be coming from the same side as the broken part so I'd wager that it was causing the issue but if anyone else has any thoughts I'm all ears.

Here's a photo of the board and how it was originally attached.

I tried contacting the seller on offerup but they basically told me to pound sand. If anyone here knows anything about this I'd be forever in your debt if I'd be able to find the component and solder it back on. Also on a somewhat related note, one side seemed to have two metal leads coming out of it and the other side only had one, but on the mobo itself both sides seemed to have only one contact.