-
The way **some browsers** render **SVG paths** cause a few visual issues especially when when **full pies** are rendered:
![64119904-2d96e700-cd9b-11e9-9663-fa4cb1425524](https://user-images.github…
-
### Is there an existing issue for this?
- [X] I have searched the existing issues
### Describe the bug
Because of lineshader's round edges, if you have high fuel capacity, the bar segments become …
-
Start of `core.algorithms.simplfy.loop()`
```python
dropped = edges[es_mask].geometry.item()
segments = list(
map(
shapely.LineString,
zip(dropped.coord…
-
Ok, clearly this wasm's size has a lot going on in the data section:
```
~/twiggy
$ twiggy top -n 10 ~/gutenberg-parser-rs/bindings/wasm/gutenberg_post_parser.debug.wasm
Shallow Bytes │ Shallo…
-
Without nodes, the intersection between edge line segments becomes visible. How should we handle this detail? Are there scientific considerations? For example, correctly "implying" the ancestor at the…
-
ALS007 restricts representation to a gradient curve.
However, in the Alignment documentation it notes that several types of curves might be used for geometric representation (refer Geometric perspect…
-
Async support would allow to run multiple call in parallel in an efficient way (since waiting for API responses will take up most of the thread time).
-
**Problem description**
'Cheatsheets' are a convenient way to summarise editing rules and examples, e.g. [GitHub Markdown Cheatsheet](https://github.com/adam-p/markdown-here/wiki/Markdown-Cheatshee…
Kevsy updated
2 weeks ago
-
After reading through the SOR core logic, I believe variable naming lacks consistency and is eventually misleading - I suggest refactoring/consolidating to improve readability:
1. `edge`/`segment` -> …
-
We should add the extraction of training samples based on annotation files (e.g., selection tables) to the segments tab, so that people can use that to build their training data sets without having to…