New package: PoliSpectralTools v0.2.0

[JuliaRegistrator]

• Registering package: PoliSpectralTools
• Repository: https://github.com/stealth-lndrs/PoliSpectralTools.jl
• Created by: @stealth-lndrs
• Version: v0.2.0
• Commit: 7ca38a735866a075f8015c0e49e1db76010ef601
• Reviewed by: @stealth-lndrs
• Reference: @JuliaRegistrator register stealth-lndrs/PoliSpectralTools.jl#2 (comment)
• Description: Biblioteca de Métodos Espectrais

[github-actions]

Hello, I am an automated registration bot. I help manage the registration process by checking your registration against a set of AutoMerge guidelines. If all these guidelines are met, this pull request will be merged automatically, completing your registration. It is strongly recommended to follow the guidelines, since otherwise the pull request needs to be manually reviewed and merged by a human.

1. New package registration

Please make sure that you have read the package naming guidelines.

2. AutoMerge Guidelines are all met! ✅

Your new package registration met all of the guidelines for auto-merging and is scheduled to be merged when the mandatory waiting period (3 days) has elapsed.

3. To pause or stop registration

If you want to prevent this pull request from being auto-merged, simply leave a comment. If you want to post a comment without blocking auto-merging, you must include the text [noblock] in your comment.

Tip: You can edit blocking comments to add [noblock] in order to unblock auto-merging.

[goerz]

Please note that registering a fork of another project is usually frowned upon. Can you clarify the relation to the original project? This would also need to be approved by @Vadinho70

The README looks a little bit like it might have been generated by an LLM, so I just want to make sure that you are aware of the LLM policies of the General registry

[stealth-lndrs]

Please note that registering a fork of another project is usually frowned upon. Can you clarify the relation to the original project? This would also need to be approved by @Vadinho70

The README looks a little bit like it might have been generated by an LLM, so I just want to make sure that you are aware of the LLM policies of the General registry

Hello, @goerz.

Thanks for concerning about authorship.

Clarifying as requested: I am a PhD student at Polytechnic School of the University of São Paulo, who recently accomplished the Spectral Methods course, whose Professor is @Vadinho70. He proposed building a Julia package containing the methods we learned during the class as a final course project, and I was responsible for taking his original project, incrementing it with features, examples and tests, and finally shaping it into an actual package with detailed docs, so that we could publish for others to use. It is still a work in progress, but this first version is quite useful already, at least for the next students of the course.

I am going to talk to him in order to have his approval here. Is a comment from him in this pull request thread enough for an approval?

Regarding the LLM usage: indeed, I coded the package with the help of an LLM. Thanks for sharing the LLM Policies, I read them and understand. I have checked the code by eye and tested the features with a subset of the examples from the classes. There are still enhancements to be done, but the current features are correct under my limited knowledge. I still haven't written a section specifying how the LLM was used, can I do this in the next version of the package?

[goerz]

Thanks for the clarification! That sounds fine to me, and good enough to move forward (and, a valid reason for registering a fork)

I would recommend including this origin story briefly, somewhere in the README

[Vadinho70]

This package was developed, with my approval, from some classroom scripts. The contributors have greatly expanded the functionality and documentation. It is very useful for anyone working with spectral methods, and I believe it would be interesting to make it public.