blog:2023-03-12
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
blog:2023-03-12 [2023/03/13 14:03] – pzhou | blog:2023-03-12 [2023/06/25 15:53] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 16: | Line 16: | ||
Anyway, we do have a functor from the original guy, to the world of comodule. Better, it is a functor for free. We now need to check that, it is fully faithful, and it is essentially surjective. Well, I have never worried about the second thing, essentially surjectivity. Can we really obtain more than what we started from? | Anyway, we do have a functor from the original guy, to the world of comodule. Better, it is a functor for free. We now need to check that, it is fully faithful, and it is essentially surjective. Well, I have never worried about the second thing, essentially surjectivity. Can we really obtain more than what we started from? | ||
- | This is where the ' | + | This is where the ' |
+ | Let's consider the reconstruction functor. First, in the commutative case. I am afraid of the infinite wrapping case, and I am not sure why it is useful in real application. So, why cannot you just add up the pushforward everywhere? Is it that simple? | ||
+ | |||
+ | Well, let's check. say you have 3 patches, you add up the contribution from patches (of course, to form a chain complex), then you can restrict to each patch and see, if they recover the original thing, and sadly, or gladly, you discovered that. On the first patch, you get $M_1 + T_{12} M_2 + T_{13} M_3$ on level 1, and then $M_{12}, M_{23}$ on level 2, and $M_{123}$ on level $3$. Something about contractiblity is important. I guess you can say, you check on the stalk level, and they all match up. But, there is no stalk in this world. So, how do you know that they do match up? Well, you can say, let's check on $M_{123}$, all good? then let's check on $U_{12}$, the part that is not in $U_{123}$, hmm? what does that even mean? don't worry let's see. What do we get? All the big patch, gives $M_{12}, M_{12}, M_{123}$, which sort of renders the intersection guy obsolete, but, that's the point. | ||
+ | |||
+ | Let's try two patch first. We have reconstructed guy | ||
+ | $$ (j_{12})_* M_{12} \to (j_1)_* M_1 + (j_2)_* M_2 $$ | ||
+ | then, we need to check that there is no 'dead loop', or ' | ||
+ | $$ (j^1)^*(j_{12})_* M_{12} \to (j^1)^*(j_1)_* M_1 + (j^1)^*(j_2)_* M_2$$ | ||
+ | Now, two things we need to use $(j^1)^*(j_1)_* M_1 = M_1$, and $(j^1)^*(j_2)_* M_2 = (j^1)^*(j_{12})_* M_{12}$. Hey, look, the second condition is exactly the so called Beck-Chevalley condition, indeed, you don't need to know it before hand, you will discover it naturally. LHS is like, you start from $U_2$, you go up and back to $U_1$, RHS is like, you start from $U_2$, you go down to the intersection, | ||
+ | |||
+ | Is that a bit sad? You went to a bigger stage, but when you come back down, you don't change? No, let's not make sentimental analogies. | ||
+ | |||
+ | Can I say that, $Q_i$ give you permanent damage? yes, sadly so. In your lifetime, you only need to apply $Q_i$ once, nothing else will restore your vision beyond $Q_i$. A limb cut is a limb cut. (hey, don't be too sentimental!). | ||
+ | |||
+ | OK, with that in place, I believe now you can do whatever you want. | ||
+ | |||
+ | False. You cannot just remember the top layer cover. That's the bad thing of playing too much with the Venn diagram, or matching in set. The gluing data is essential. Consider the line bundle on $\P^1$. How do we reconstruct $O(1)$ from line bundle on $\P^1$? One way of doing so is like, you remember the object (object itself, not some isomorphism class) when restricted to each patch, and ask that they glue honestly. Sure, you can say, here is " | ||
+ | |||
+ | When we say, glue, we mean on each local piece, there are some standard building block. But, there are interesting automorphisms. When stuff from more global places restricts to local piece, we need to specify, how do we ' | ||
blog/2023-03-12.1678716207.txt.gz · Last modified: 2023/06/25 15:53 (external edit)