Sascha Timme

https://github.com/NonlinearOscillations/HarmonicBalance.jl/blob/44349d505de8d537bba8b4fd409949fa9ce8afb4/src/solve_homotopy.jl#L241-L247 Is this the main part where you call HC and where your performance bottleneck is? I only glanced over your intro, but if you really do parameter sweeps then...

> Could you elude on why it would lead to path failures? Is it because the homotopy "step size" is too small? If a solution path passes a singularity closely...

Interesting that there are so many failures. My guess would be that you are actually operating intentionally close to singularities in the parameter space and thus maybe more tricky. Definitely...

Also not 100% sure this is applicable, but for me it looks like you actually want to sample the discriminant of the steady state problem not the steady state space....

We are seeing the same periodic failure

The React Native packager (now extracted as [metro-bundler](https://github.com/facebook/metro-bundler)) has as a hardcoded resolution rule to check for the `name[.platform].js` pattern: https://github.com/facebook/metro-bundler/blob/74e78ee43f73d0452dcce0db0887f055cf7abbee/packages/metro-bundler/src/node-haste/lib/parsePlatformFilePath.js#L30