Giter Site home page Giter Site logo

mlresearch.github.io's People

Contributors

albanie avatar lawrennd avatar mreid avatar mrksr avatar tnaumann avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

mlresearch.github.io's Issues

Use of `number` versus `volume` field in (generated) BibTeX output

Dear all,

Thanks for maintaining this awesome institution! I have one—maybe naive and nitpicky—question about the generated BibTeX output: it is my understanding that number should be used since we are dealing with a series. The official BibLaTeX manual on p. 24 mentions the following:

The number of a journal or the volume/number of a book in a series

Whereas for volume, the explanation is:

The volume of a multi-volume book or a periodical.

My question is now whether it would be possible to change this.

Let's take a recent entry as a running example:

@InProceedings{pmlr-v196-hacker22a,
  title = 	 {On the Surprising Behaviour of \texttt{node2vec}},
  author =       {Hacker, Celia and Rieck, Bastian},
  booktitle = 	 {Proceedings of Topological, Algebraic, and Geometric Learning Workshops 2022},
  pages = 	 {142--151},
  year = 	 {2022},
  editor = 	 {Cloninger, Alexander and Doster, Timothy and Emerson, Tegan and Kaul, Manohar and Ktena, Ira and Kvinge, Henry and Miolane, Nina and Rieck, Bastian and Tymochko, Sarah and Wolf, Guy},
  volume = 	 {196},
  series = 	 {Proceedings of Machine Learning Research},
  month = 	 {25 Feb--22 Jul},
  publisher =    {PMLR},
  pdf = 	 {https://proceedings.mlr.press/v196/hacker22a/hacker22a.pdf},
  url = 	 {https://proceedings.mlr.press/v196/hacker22a.html},
  abstract = 	 {Graph embedding techniques are a staple of modern graph learning research. When using embeddings for downstream tasks such as classification, information about their stability and robustness, i.e., their susceptibility to sources of noise, stochastic effects, or specific parameter choices, becomes increasingly important. As one of the most prominent graph embedding schemes, we focus on \texttt{node2vec} and analyse its embedding quality from multiple perspectives. Our findings indicate that embedding quality is unstable with respect to parameter choices, and we propose strategies to remedy this in practice.}
}

Example with volume

If I use volume, I get the following output:

image

Example with number

If I use number, on the other hand, I get the following output:

image

This output seems to be somehow cleaner and less clunky to me, but I admit it's

Example with @article

Notice that this only pertains to the @inproceedings entries; everything looks different of course with journal articles:

image

Summary

Sorry for this weird question—I would love to understand this phenomenon better; probably I am using BibLaTeX wrong... Feel free to close if this question makes no sense, of course!

Main rss feed generates broken links

The RSS feed of the volumes (http://proceedings.mlr.press/feed.xml) is broken insofar as the links it generates are missing a slash.

For example for the first volume the item is

<item>
<title>v1</title>
<description>Gaussian Processes in Practice</description>
<link>http://proceedings.mlr.pressv1</link>
<guid isPermaLink="true">http://proceedings.mlr.press/v1</guid>
</item>

Instead of <link>http://proceedings.mlr.press/v1</link>.

Since the guid below is correct, it seems that the link is simply missing the prepend: '/' in the /assets/rss/feed.xml` file:

<link>{{ repository.name | prepend: site.baseurl | prepend: site.url }}</link>
<guid isPermaLink="true">{{ repository.name | prepend: '/' | prepend: site.baseurl | prepend: site.url }}</guid>

Certificate Issue when accessing via HTTPs

At the moment, it seems that the site has a certificate issue when accessing via HTTPS.

image

The current certificate seems to belong to www.github.com.

image

I checked on both Safari and Chrome; they have the same issue. I access the site from Germany.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo 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.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.