2025-04-28-linrec #71
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
👋 Thanks for your submission! We have successfully built your website and we will push it shortly to the URL https://d2jud02ci9yv69.cloudfront.net/2025-04-28-linrec-71/blog/linrec/ ! |
|
👋 Thanks for your submission! We have successfully built your website and we will push it shortly to the URL https://d2jud02ci9yv69.cloudfront.net/2025-04-28-linrec-71/blog/linrec/ ! |
|
👋 Thanks for your submission! We have successfully built your website and we will push it shortly to the URL https://d2jud02ci9yv69.cloudfront.net/2025-04-28-linrec-71/blog/linrec/ ! |
|
👋 Thanks for your submission! We have successfully built your website and we will push it shortly to the URL https://d2jud02ci9yv69.cloudfront.net/2025-04-28-linrec-71/blog/linrec/ ! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
OpenReview Submission Thread
https://openreview.net/forum?id=1SK8PYL02N
Checklist before opening a PR
I am opening a pull request against the
mainbranch of the2025repo.My post and all associated references to it are all lowercase, i.e
The title of my PR is exactly the name of my markdown file
_posts/2025-04-28-[submission-name].mdwould require a PR name2025-04-28-[submission-name]I have anonymized my post: my author's list is
Anonymous, and there is no potentialcontent which can reveal my/my collaborators identities.
My post matches the formatting requirements, including (but not limited to):
your PR automatically being closed!):
_posts/with the format_posts/2025-04-28-[submission-name].md(or.html)assets/img/2025-04-28-[submission-name]/assets/html/2025-04-28-[submission-name]/assets/bibliography/2025-04-28-[submission-name].bibdescriptionfield of my front-mattertocfield of my front-matter.bibtexfile as per the sample postAny other comments
This is an initial draft to test the submission system.