Comments (4)
I finally found a solution for the problem that using version selector leads to a 404
error. Since the problem did not occur locally on http://localhost:8000/
, I could only test it directly on pathpy.net
. I checked the mentioned parts of the Documentation again and now everything works again as it should.
I think this example highlights very well why it is nice to have a versioned documentation. When we finally have a first stable release on pip
and publish the corresponding stable
documentation page, then no matter what problems might currently occur on the dev
documentation, the stable
documentation corresponding to each release will still be available.
from pathpyg.
As soon as I have completed the refactoring of the PathData
class (and as soon as we have expanded the test coverage a bit more), we can release a first stable
version. After this refactoring is done, I do not expect substantial API changes.
from pathpyg.
Sorry, I am currently working on a fix for the version selector returning a 404 error. During that the documentation might have not been available for a few minutes. This might be because of this.
from pathpyg.
No need to be sorry and thanks for your great work!
from pathpyg.
Related Issues (20)
- Unintended Boolean Conversions and Ordering Changes in `IndexMap`
- Extend `IndexMap.to_idxs(...)` to any shape
- `TemporalGraph.get_window(...)` and `TemporalGraph.get_snapshot` behaviour not as expected HOT 2
- Refactor `lift_order`-logic from `MultiOrderModel` to `algorithms`
- Change filenames
- Add convenience method to `MultiOrderModel` to create a `PyG`-`Data` object that can be used by DBGNN HOT 1
- Switch from Global `device`-`config` to `tensor`-wise configuration
- Extend `append_DAG` to work with nodes appearing at multiple points in time
- Setter for node/edge attributes not working
- Plot to tikz/pdf currently not working HOT 1
- Implement functions to read/write Graphs to CSV
- inefficient calculation of temporal paths HOT 1
- How should we handle `num_nodes`? HOT 3
- Should we implement a zeroth order layer in MultiOrderModel?
- `PyG` is going to deprecate `TemporalData`
- import and plotting fail for (some) netzschleuder dataset
- Decrease memory footprint in `MultiOrderModel`
- Refactor DAGData and MultiOrderModel
- Improve use of IndexMap in `Graph.from_edge_list`
- Port new functions from ML4Nets course
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
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.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from pathpyg.