github-starred/cs249r_book
2
0
Fork 0
mirror of https://github.com/harvard-edge/cs249r_book.git synced 2026-05-08 02:28:25 -05:00
Code Issues 85 Packages Projects Releases 24 Wiki Activity

[GH-ISSUE #304] Suggestion: Cite the following papers #1351

New Issue
Closed
opened 2026-04-11 07:44:28 -05:00 by GiteaMirror · 7 comments
GiteaMirror commented 2026-04-11 07:44:28 -05:00
Owner
Copy Link

Originally created by @FinAminToastCrunch on GitHub (Jul 2, 2024).
Original GitHub issue: https://github.com/harvard-edge/cs249r_book/issues/304

In reference to Ethical Considerations on Pruning, I would suggest citing:

Tran, Cuong, et al. "Pruning has a disparate impact on model accuracy." Advances in neural information processing systems 35 (2022): 17652-17664.

As it discusses how pruning can harm accuracy with respect to inferencing on certain ethnicities.

In reference to Establishing Criteria for Pruning, I believe these two papers would be relevant to cite for the portions on importance scores as they tie together more recent work concerning gradient flow and neuron magnitude:

J. Rachwan, D. Z ̈ugner, B. Charpentier, S. Geisler, M. Ayle, and
S. G ̈unnemann, “Winning the lottery ahead of time: Efficient early
network pruning,” in International Conference on Machine Learning,
ICML 2022, 17-23 July 2022, Baltimore, Maryland, USA (K. Chaudhuri,
S. Jegelka, L. Song, C. Szepesv ́ari, G. Niu, and S. Sabato, eds.),
vol. 162 of Proceedings of Machine Learning Research, pp. 18293–
18309, PMLR, 2022.

E. S. Lubana and R. P. Dick, “A gradient flow framework for analyzing
network pruning,” CoRR, vol. abs/2009.11839, 2020.

Originally created by @FinAminToastCrunch on GitHub (Jul 2, 2024). Original GitHub issue: https://github.com/harvard-edge/cs249r_book/issues/304 In reference to [Ethical Considerations on Pruning](https://harvard-edge.github.io/cs249r_book/contents/optimizations/optimizations.html#legal-and-ethical-considerations), I would suggest citing: Tran, Cuong, et al. "Pruning has a disparate impact on model accuracy." Advances in neural information processing systems 35 (2022): 17652-17664. As it discusses how pruning can harm accuracy with respect to inferencing on certain ethnicities. In reference to [Establishing Criteria for Pruning](https://harvard-edge.github.io/cs249r_book/contents/optimizations/optimizations.html#establishing-a-criteria-for-pruning), I believe these two papers would be relevant to cite for the portions on importance scores as they tie together more recent work concerning gradient flow and neuron magnitude: J. Rachwan, D. Z ̈ugner, B. Charpentier, S. Geisler, M. Ayle, and S. G ̈unnemann, “Winning the lottery ahead of time: Efficient early network pruning,” in International Conference on Machine Learning, ICML 2022, 17-23 July 2022, Baltimore, Maryland, USA (K. Chaudhuri, S. Jegelka, L. Song, C. Szepesv ́ari, G. Niu, and S. Sabato, eds.), vol. 162 of Proceedings of Machine Learning Research, pp. 18293– 18309, PMLR, 2022. E. S. Lubana and R. P. Dick, “A gradient flow framework for analyzing network pruning,” CoRR, vol. abs/2009.11839, 2020.
GiteaMirror added the area: tools label 2026-04-11 07:44:28 -05:00
GiteaMirror commented 2026-04-11 07:44:30 -05:00
Author
Owner
Copy Link

@profvjreddi commented on GitHub (Jul 4, 2024):

@FinAminToastCrunch The link you shared is not working. Could you update the link so I can take at which part you are referring to here.

<!-- gh-comment-id:2209204569 --> @profvjreddi commented on GitHub (Jul 4, 2024): @FinAminToastCrunch The link you shared is not working. Could you update the link so I can take at which part you are referring to here.
GiteaMirror commented 2026-04-11 07:44:31 -05:00
Author
Owner
Copy Link

@FinAminToastCrunch commented on GitHub (Jul 4, 2024):

Fixed:

https://harvard-edge.github.io/cs249r_book/contents/optimizations/optimizations.html#legal-and-ethical-considerations

<!-- gh-comment-id:2209323852 --> @FinAminToastCrunch commented on GitHub (Jul 4, 2024): Fixed: https://harvard-edge.github.io/cs249r_book/contents/optimizations/optimizations.html#legal-and-ethical-considerations
GiteaMirror commented 2026-04-11 07:44:32 -05:00
Author
Owner
Copy Link

@profvjreddi commented on GitHub (Jul 4, 2024):

Thanks Fin! Do you think you could issue a PR so that I could review it and
merge it in? I will edit it if needed after you issue a PR.

On Thu, Jul 04, 2024 at 12:32 PM, Fin Amin @.***> wrote:

Fixed:

https://harvard-edge.github.io/cs249r_book/contents/optimizations/
optimizations.html#legal-and-ethical-considerations

—
Reply to this email directly, view it on GitHub
https://github.com/harvard-edge/cs249r_book/issues/304#issuecomment-2209323852,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABT6DFCX5CGCGD27HY2FEBLZKV2K7AVCNFSM6AAAAABKGWEZOSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMBZGMZDGOBVGI
.
You are receiving this because you commented.Message ID:
@.***>

<!-- gh-comment-id:2209338244 --> @profvjreddi commented on GitHub (Jul 4, 2024): Thanks Fin! Do you think you could issue a PR so that I could review it and merge it in? I will edit it if needed after you issue a PR. On Thu, Jul 04, 2024 at 12:32 PM, Fin Amin ***@***.***> wrote: > Fixed: > > https://harvard-edge.github.io/cs249r_book/contents/optimizations/ > optimizations.html#legal-and-ethical-considerations > > — > Reply to this email directly, view it on GitHub > <https://github.com/harvard-edge/cs249r_book/issues/304#issuecomment-2209323852>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/ABT6DFCX5CGCGD27HY2FEBLZKV2K7AVCNFSM6AAAAABKGWEZOSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMBZGMZDGOBVGI> > . > You are receiving this because you commented.Message ID: > ***@***.***> >
GiteaMirror commented 2026-04-11 07:44:32 -05:00
Author
Owner
Copy Link

@profvjreddi commented on GitHub (Jul 4, 2024):

And just as FYI. I typically avoid incorporating overly cutting-edge
material into the book. The criterion for inclusion is that the industry
must be actively adopting and utilizing the methods discussed. This
approach ensures the content remains relevant and avoids delving into an
excessive number of rapidly evolving topics. Does that make sense?

On Thu, Jul 04, 2024 at 12:44 PM, Janapa Reddi, Vijay @.***>
wrote:

Thanks Fin! Do you think you could issue a PR so that I could review it
and merge it in? I will edit it if needed after you issue a PR.

Vijay Janapa Reddi, Ph. D. |
John L. Loeb Associate Professor of Engineering and Applied Sciences |
John A. Paulson School of Engineering and Applied Sciences |
Science and Engineering Complex (SEC) | 150 Western Ave, Room #5.305 |
Boston, MA 02134 |
Harvard University | My Website
http://scholar.harvard.edu/vijay-janapa-reddi | Google Scholar
https://scholar.google.com/citations?hl=en&user=gy4UVGcAAAAJ&view_op=list_works&sortby=pubdate
| Edge Computing Lab https://edge.seas.harvard.edu | Book Meeting
https://fantastical.app/vjreddi/ | Contact Admin
https://scholar.harvard.edu/vijay-janapa-reddi/contact |

On Thu, Jul 04, 2024 at 12:32 PM, Fin Amin @.***>
wrote:

Fixed:

https://harvard-edge.github.io/cs249r_book/contents/optimizations/
optimizations.html#legal-and-ethical-considerations

—
Reply to this email directly, view it on GitHub
https://github.com/harvard-edge/cs249r_book/issues/304#issuecomment-2209323852,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABT6DFCX5CGCGD27HY2FEBLZKV2K7AVCNFSM6AAAAABKGWEZOSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMBZGMZDGOBVGI
.
You are receiving this because you commented.Message ID:
@.***>

<!-- gh-comment-id:2209339695 --> @profvjreddi commented on GitHub (Jul 4, 2024): And just as FYI. I typically avoid incorporating overly cutting-edge material into the book. The criterion for inclusion is that the industry must be actively adopting and utilizing the methods discussed. This approach ensures the content remains relevant and avoids delving into an excessive number of rapidly evolving topics. Does that make sense? On Thu, Jul 04, 2024 at 12:44 PM, Janapa Reddi, Vijay ***@***.***> wrote: > Thanks Fin! Do you think you could issue a PR so that I could review it > and merge it in? I will edit it if needed after you issue a PR. > > Vijay Janapa Reddi, Ph. D. | > John L. Loeb Associate Professor of Engineering and Applied Sciences | > John A. Paulson School of Engineering and Applied Sciences | > Science and Engineering Complex (SEC) | 150 Western Ave, Room #5.305 | > Boston, MA 02134 | > Harvard University | My Website > <http://scholar.harvard.edu/vijay-janapa-reddi> | Google Scholar > <https://scholar.google.com/citations?hl=en&user=gy4UVGcAAAAJ&view_op=list_works&sortby=pubdate> > | Edge Computing Lab <https://edge.seas.harvard.edu> | Book Meeting > <https://fantastical.app/vjreddi/> | Contact Admin > <https://scholar.harvard.edu/vijay-janapa-reddi/contact> | > > > On Thu, Jul 04, 2024 at 12:32 PM, Fin Amin ***@***.***> > wrote: > > Fixed: > > https://harvard-edge.github.io/cs249r_book/contents/optimizations/ > optimizations.html#legal-and-ethical-considerations > > — > Reply to this email directly, view it on GitHub > <https://github.com/harvard-edge/cs249r_book/issues/304#issuecomment-2209323852>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/ABT6DFCX5CGCGD27HY2FEBLZKV2K7AVCNFSM6AAAAABKGWEZOSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMBZGMZDGOBVGI> > . > You are receiving this because you commented.Message ID: > ***@***.***> > >
GiteaMirror commented 2026-04-11 07:44:34 -05:00
Author
Owner
Copy Link

@FinAminToastCrunch commented on GitHub (Jul 4, 2024):

Done!

And yes, makes sense.

<!-- gh-comment-id:2209513858 --> @FinAminToastCrunch commented on GitHub (Jul 4, 2024): Done! And yes, makes sense.
GiteaMirror commented 2026-04-11 07:44:35 -05:00
Author
Owner
Copy Link

@profvjreddi commented on GitHub (Jul 8, 2024):

Dealt with in issue https://github.com/harvard-edge/cs249r_book/pull/306 and PR

<!-- gh-comment-id:2215100625 --> @profvjreddi commented on GitHub (Jul 8, 2024): Dealt with in issue https://github.com/harvard-edge/cs249r_book/pull/306 and PR
GiteaMirror commented 2026-04-11 07:44:36 -05:00
Author
Owner
Copy Link

@profvjreddi commented on GitHub (Jul 30, 2024):

Thanks @FinAminToastCrunch I finally got a chance to review the changes and make some tweaks an close it.

<!-- gh-comment-id:2258925912 --> @profvjreddi commented on GitHub (Jul 30, 2024): Thanks @FinAminToastCrunch I finally got a chance to review the changes and make some tweaks an close it.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area: book
area: collabs
area: kits
area: socratiq
area: tinytorch
area: tools
area: website
bug
dependencies
format: epub
format: pdf
link-health
link-rot
priority-high
pull-request
Mirrored from GitHub Pull Request
 staffml
type: bug
type: citation
type: code
type: errata
type: improvement
type: new
type: question
vault-sli
No Label area: tools
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/cs249r_book#1351
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?