m4r35n357 said:
I'm trying to get someone to actually read (not skim) my stuff and point out actual mistakes in my notation
This is the official statement: I'm afraid we are not able to discuss personal work as we are no reviewers of papers.
Inofficial, I like to add a few remarks. Your ODE solver requires a login. This is a hurdle not many will be willing to take; me, for example. Then you provide a paper from Jorba and Zou from 2004 whose copyright situation is not clear, and which is possibly not peer reviewed. At least I cannot tell from the link you gave. This means, that it is hard to tell which value this paper has, i.e. whether it contains flaws or not. But let us assume that they presented a valid algorithm for the moment. In order to understand what you might have done, one has to read this paper, which is factually almost another peer review. You cannot expect anyone to do this. However, we assumed that the paper is correct. Then you are searching for someone who is familiar with its content. Something yourself said is unlikely:
m4r35n357 said:
My aim is to explain the Jorba-Zou method more simply and thoroughly, because it deserves more attention.
At least I have read your comment about its attention in this way.
So let us turn to your second link. It leads to a peer reviewed paper, but only to the abstract. It is not clear how the two papers are related, and how your work fits in here. I assume, this is your attachment. It is the next hurdle. I downloaded it in order to be able to write this comment, but I do not like it to be forced to download unknown files. And I'm probably not alone, which shrinks your potential readership even further.
Anyway, I skimmed your work. And here I am indeed experienced in reading papers about algorithms. It doesn't need a closer look to see that it lacks essential parts. The algorithm covers - benevolently counted - 16 lines. The rest are statements and examples, which are not important. So neither is your algorithm documented in a serious way, nor did you a) prove that it works, b) added an analysis of space and time, or c) analyzed the accuracy of your procedure. You didn't even prove it comes to a hold! Those are essential parts of a documentation of an algorithm.
To summarize the above: There are too many hurdles and severe gaps in preparation and presentation.
I'm sorry that this doesn't match your expectations as I see that you put quite some effort in it. The most important recommendation I would give is: Concentrate on the algorithm and its needs and forget examples, links and similar. Those should only build the frame. The ratio 780 : 4900 (section 2 : entire document) is not what one would expect from a documentation.
This thread is closed.