@halirutan However, the lack of the ability to download the test suite is serious deficiency. For now, couldn't we just drop in the html from Rubi's current website for downloading the test suite in Mathematica, Maple, Maxima and Axiom syntax?
@halirutan I just tried going to https://RuleBasedIntegration.org/ and got the GitHub error message to use the correct case. Can you make it so https://RuleBasedIntegration.org/ automatically goes to https://rulebasedintegration.org/? The former is a little easier to read, and MS Windows users are not use to case sensitivity.
@halirutan Now my browser (Google Chrome) is redirecting to the lower case version like yours. Apparently, Chrome sees the lower case version of the GitHub Rubi website in its History, and automatically uses that. I tried to delete my history to test my hypothesis, but to no avail...
But the first time I tried it today, I did get bounced.
@AlbertRich What really matters is if the DNS can resolve RuleBasedIntegration.org to the correct IP address. You can try https://mxtoolbox.com/DNSLookup.aspx and you'll find that it works.
What I am thinking is that the Dewey Decimal number of rules can be ascertained from the nested grouping of cells in the source files.
The current status is as follows: I'm programmatically opening all you rule-notebooks and extract the code cells an put them into the zipped .m files for the package.
This all is done in a loop until all your notebooks are processed. Now, let's assume I use a global counter
i that is increased with each code cell that I write to the .m files. At the moment of processing, I know which notebook I'm processing and which code-cell I'm processing and I have the global counter i. It is very easy to have a mapping function
reference[i_] := {notebook, codecell}
The only slightly non-trivial part is, how I can store
i in the definition of the current rule without breaking anything. But let's assume we have this solved, then I can extract i from each rule and with the help of reference I know instantly where it is defined. I know the exact cell inside the notebook.
So in the best case, I can create for each used rule in
Steps[Int[expr, var]] a button, that automatically opens the right notebook and cell where this rule is defined.
When loading a .m rule file with
Get all comments are ignored and you can never access them again.
This would eliminate the ModifyRule pass.
@halirutan Forget assuming anything about DownValues. I propose:
- Building .m files for the Rubi package like you currently do but with comments giving Reference, Derivation, Basis, and the rule's source file location. E.g. the comment "Derivation: Integration by parts"
- If loading without step information, load the .m files as Mathematica normally does. Thus each rule would be free of any step info.
- If loading with step information, parse the .m files yourself extracting the comments and rule definition. Then define the rule with all this step info. Thus each rule would only have to be defined once, and there would be no second ModifyRule pass. Yea!
Obviously this is a long term project, I am not suggesting you do now.
I assume you meant "wouldn't"...
(a) will definitely be the case. To which degree, I'm not sure.
(b) I would really like to hope this happens. But I have to say that for instance my Mathematica plugin for IntelliJ has right now 47000 downloads and it is open source from the beginning in 2013. Although I have support from various users that test things and report bugs, the one genious programmer, that knows Mathematica and Java well and jumpes on board is still missing.
@AlbertRich What do you think? If we make another button on the web-site for the test suite that links to your page, are we then ready to spread it to the world?