is set in compile. The single path execution code does not yet support
        all use cases. We fallback to the existing v1 execution paths if your
        model contains the following:
        1.  `sample_weight_mode` in compile
        2.  `weighted_metrics` in compile
        3.  v1 optimizer
        4.  target tensors in compile If you are experiencing any issues because

return Element{ rand.Uint64() & maskLow52Bits, rand.Uint64() & maskLow52Bits, rand.Uint64() & maskLow52Bits, rand.Uint64() & maskLow52Bits, rand.Uint64() & maskLow52Bits, } } // weirdLimbs can be combined to generate a range of edge-case field elements. // 0 and -1 are intentionally more weighted, as they combine well. var ( weirdLimbs51 = []uint64{ 0, 0, 0, 0, 1, 19 - 1, 19, 0x2aaaaaaaaaaaa, 0x5555555555555, (1 << 51) - 20, (1 << 51) - 19, (1 << 51) - 1, (1 << 51) - 1, (1 << 51) - 1, (1 << 51) - 1, }...

return Element{ rand.Uint64() & maskLow52Bits, rand.Uint64() & maskLow52Bits, rand.Uint64() & maskLow52Bits, rand.Uint64() & maskLow52Bits, rand.Uint64() & maskLow52Bits, } } // weirdLimbs can be combined to generate a range of edge-case field elements. // 0 and -1 are intentionally more weighted, as they combine well. var ( weirdLimbs51 = []uint64{ 0, 0, 0, 0, 1, 19 - 1, 19, 0x2aaaaaaaaaaaa, 0x5555555555555, (1 << 51) - 20, (1 << 51) - 19, (1 << 51) - 1, (1 << 51) - 1, (1 << 51) - 1, (1 << 51) - 1, }...

    * These `dependencies` are run before the normal parameter dependencies. And normal dependencies are run too. They can be combined.
    * Dependencies declared in a router are executed first, then the ones defined in *path operation decorators*, and then the ones declared in normal parameters. They are all combined and executed.