Giter VIP home page Giter VIP logo

Comments (2)

plonghi avatar plonghi commented on August 16, 2024
  1. I implemented a set of basic global checks on monodromies. The product of monodromies from branch points and irregular singularities does not match with the monodromy at infinity, in at least two examples: seeding_type_III_A and coset_D_4.
    Fixing this is somewhat urgent, as it points to potentially serious issues with trivialization of the covering.

UPDATE: it seems that the issue arises in configurations of D-type, where two sheets are identically zero everywhere. The discrepancy between monodromies at branch points (plus irregular singualrities) and the monodromy at infinity involves precisely the switching of the two null sheets.
This is now correctly handled in seeding_type_III_A and in coset_D_4. But, the problem now arises in D_4_AD_from_SO_8.
Needs further investigation, to find a way of determining this tricky piece of the monodromy. At least, the problem does not appear to be too severe, but will still lead to tangible trouble with trivializing covers, and creating consistent networks.

from loom.

plonghi avatar plonghi commented on August 16, 2024
  1. In this example http://het-math2.physics.rutgers.edu/loom/plot?data=SU_3_N_f_6 there appear to be inconsistent labeling of S-walls by roots. This is not an issue due trivialization, in fact the direct check on global consistency on monodromy indicates that monodromies are OK.
    The issue is with the routine that assigns roots to single S-walls. It fails at particular phases: below I post a few examples (see picture for the precise phase/step)
    a) In plot 7 the S-wall emanating from the branch point on the left is green, it should be purple.
    b) In plot 17 the two green S-walls in the middle intersect each other. This means they can't be of the same root type.
    c) In plot 64 the S-wall emanating from the bottom-right branch point, and flowing downwards should be Purple, not Blue.
    d) In the last picture I zoomed in on an artifact occurring close to the bottom-left branch point at step 15, I don't have a good understanding of this artifact right now, bt it's clearly important to correct these things.

a)
screenshot from 2016-02-26 19 28 17
b)
screenshot from 2016-02-26 19 28 49
c)
screenshot from 2016-02-26 19 29 18
d)
screenshot from 2016-02-26 19 23 04

from loom.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.