Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 7415901
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 29, 20262026-05-29T07:23:18+00:00 2026-05-29T07:23:18+00:00

Suppose we have a DAG with one source. I would like to find nodes

  • 0

Suppose we have a DAG with one source. I would like to find nodes n such that any complete path from the source runs through n (i.e. n dominates all sinks). In other words: if we removed all the succesors of n, then all paths would end in n. The problem is that nodes are incrementally marked as deleted in the DAG. As nodes are marked deleted, other nodes can start to satisfy the above property. How can I efficiently detect this as it happens?

Bonus points if the data structure can do this with multiple sources in a more efficient way than running the algorithm for a single source separately on each of the sources.

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-29T07:23:19+00:00Added an answer on May 29, 2026 at 7:23 am

    Topologically sort this DAG to establish some order for its nodes. For each node, its value would be the number of outgoing edges from all preceding nodes minus the number of incoming edges to all preceding nodes and current node. Value for “dominator” node is always zero.

    After some node is marked “deleted”, put its predecessors and successors to priority queue. Priority is determined by the topological sort order. Update values for all nodes, following the “deleted” node (add the number of incoming nodes and subtract the number of outgoing nodes for this node). At the same time (in same order) decrement value for each node between predecessor node in the priority queue and the “deleted” node and increment value for each node, starting from successor node in the priority queue. Stop when some node’s value is decremented to zero. This is a new “dominator” node. If all “dominator” nodes needed, continue until the end of the graph.

    delete(delNode):
      for each predecessor in delNode.predecessors: queue.add(predecessor)
      for each successor in delNode.successors: queue.add(successor)
      for each node in DAG:
        if queue.top.priority == node.priority > delNode.priority:
          ++accumulator
    
        node.value += accumulator
        if node.value == 0: dominatorDetected(node)
    
        if node.priority == delNode.priority:
          accumulator += (delNode.predecessors.size - delNode.successors.size)
          node.value = -1
    
        if queue.top.priority == node.priority:
          queue.pop()
          if node.priority < delNode.priority:
            --accumulator
    
        if queue.empty: stop
    

    For multiple sources case, it is possible to use the same algorithm, but keep a list of “values” for each node, one value for each source. Algorithm complexity is O(Nodes * Sources), the same as for independent search on each of the sources. But the program may be made more efficient if vectorization is used. “values” may be processed in parallel with SIMD instructions. Modern compilers may do automatic vectorization to acieve this.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

Suppose i have one table that holds Blogs. The schema looks like : ID
I have a DAG representing a list of properties. These properties are such that
Suppose I have 2 tables, query and rank. I would like to know if
Suppose i have an XML file, that i use as local database, like this):
Suppose we have buyers and sellers that are trying to find each other in
Suppose I have a data frame, df, that looks like: f t1 t2 t3
Suppose I have a class that looks like this: class Derived : // some
Suppose I have a stringbuilder in C# that does this: StringBuilder sb = new
Suppose I have: Toby Tiny Tory Tily Is there an algorithm that can easily
Suppose I have a table called Companies that has a DepartmentID column. There's also

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.