Skip to content

2025-04-28-gradient-similarity-in-cnns-a-new-perspective-on-class-concept-representation#222

Closed
Emadeldeen-Hamdan wants to merge 11 commits intoiclr-blogposts:mainfrom
Emadeldeen-Hamdan:2025-04-28-gradient-similarity-in-cnns-a-new-perspective-on-class-concept-representation
Closed

2025-04-28-gradient-similarity-in-cnns-a-new-perspective-on-class-concept-representation#222
Emadeldeen-Hamdan wants to merge 11 commits intoiclr-blogposts:mainfrom
Emadeldeen-Hamdan:2025-04-28-gradient-similarity-in-cnns-a-new-perspective-on-class-concept-representation

Conversation

@Emadeldeen-Hamdan
Copy link
Contributor

@Emadeldeen-Hamdan Emadeldeen-Hamdan commented Apr 1, 2025

OpenReview Submission Thread

Checklist before opening a PR

  • I am opening a pull request against the main branch of the 2025 repo.

  • My post and all associated references to it are all lowercase, i.e

      2025-04-28-Sample-Test.md               -> 2025-04-28-sample-test.md
      assets/img/2025-04-28-Sample-Test/ 	-> assets/img/2025-04-28-sample-test/
    
  • The title of my PR is exactly the name of my markdown file

    • i.e. _posts/2025-04-28-[submission-name].md would require a PR name 2025-04-28-[submission-name]
  • I have anonymized my post: my author's list is Anonymous, and there is no potential
    content which can reveal my/my collaborators identities.

  • My post matches the formatting requirements, including (but not limited to):

    • I have ONLY MODIFIED files in the following locations (failure to do so will result in
      your PR automatically being closed!):
      • a Markdown (or HTML) file in _posts/ with the format _posts/2025-04-28-[submission-name].md (or .html)
      • static image assets added to assets/img/2025-04-28-[submission-name]/
      • interactive HTML figures added to assets/html/2025-04-28-[submission-name]/
      • citations in a bibtex file in assets/bibliography/2025-04-28-[submission-name].bib
    • I have a short 2-3 sentence abstract in the description field of my front-matter
    • I have a table of contents, formatted using the toc field of my front-matter
    • My bibliography is correctly formatted, using a .bibtex file as per the sample post

Any other comments

@Emadeldeen-Hamdan Emadeldeen-Hamdan changed the title 2025-04-28-gradien- similarity-in-cnns-a-new-perspective-on-class-concept-representation 2025-04-28-gradient-similarity-in-cnns-a-new-perspective-on-class-concept-representation Apr 1, 2025
@Emadeldeen-Hamdan
Copy link
Contributor Author

@busycalibrating can you assist?

@Emadeldeen-Hamdan
Copy link
Contributor Author

@busycalibrating the camera-ready version is ready to be merged.

@busycalibrating
Copy link
Member

@Emadeldeen-Hamdan there seem to be a few merge conflicts; could you see if you can resolve them? Let me know if you can't figure it out; perhaps you can pull/merge in main and resolve the conflicts on your end first

@Emadeldeen-Hamdan
Copy link
Contributor Author

Hi @busycalibrating,
Thank you for the help. I fixed the all the conflicts. There is this new error that I did not know how to solve. Is it on my side?

@github-actions
Copy link
Contributor

⚠️ We have detected a problem with your submission! ⚠️

You can only add/change/remove files related to your post, i.e. files that match one of these patterns: <_posts/SLUG.md, assets/img/SLUG/..., assets/html/SLUG/..., assets/bibliography/SLUG.bib>. But we found that you changed the following: <.github/workflows/filter-files.yml>. Also, make sure your PR's title (2025-04-28-gradient-similarity-in-cnns-a-new-perspective-on-class-concept-representation) matches your post's slug!

Please make the aforementioned changes and re-submit :)

@Emadeldeen-Hamdan
Copy link
Contributor Author

I tried fixing the new error by changing toruns-on: ubuntu-latest from runs-on: ubuntu-20.04, but it looks like I'm not authorized to do so @busycalibrating. Thanks

@Emadeldeen-Hamdan Emadeldeen-Hamdan deleted the 2025-04-28-gradient-similarity-in-cnns-a-new-perspective-on-class-concept-representation branch September 21, 2025 01:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants