Menu
▾
▴
maxima-discuss — Maxima discussion list
You can subscribe to this list here.
| 2014 |
Jan
|
Feb
(232) |
Mar
(323) |
Apr
(383) |
May
(359) |
Jun
(435) |
Jul
(252) |
Aug
(172) |
Sep
(265) |
Oct
(263) |
Nov
(350) |
Dec
(359) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2015 |
Jan
(267) |
Feb
(220) |
Mar
(311) |
Apr
(269) |
May
(388) |
Jun
(403) |
Jul
(172) |
Aug
(399) |
Sep
(364) |
Oct
(269) |
Nov
(357) |
Dec
(468) |
| 2016 |
Jan
(618) |
Feb
(592) |
Mar
(625) |
Apr
(516) |
May
(375) |
Jun
(155) |
Jul
(346) |
Aug
(262) |
Sep
(346) |
Oct
(291) |
Nov
(333) |
Dec
(335) |
| 2017 |
Jan
(436) |
Feb
(460) |
Mar
(370) |
Apr
(189) |
May
(252) |
Jun
(272) |
Jul
(286) |
Aug
(293) |
Sep
(303) |
Oct
(331) |
Nov
(346) |
Dec
(273) |
| 2018 |
Jan
(295) |
Feb
(343) |
Mar
(265) |
Apr
(290) |
May
(233) |
Jun
(201) |
Jul
(234) |
Aug
(125) |
Sep
(287) |
Oct
(322) |
Nov
(274) |
Dec
(293) |
| 2019 |
Jan
(406) |
Feb
(255) |
Mar
(418) |
Apr
(187) |
May
(247) |
Jun
(282) |
Jul
(84) |
Aug
(108) |
Sep
(175) |
Oct
(161) |
Nov
(215) |
Dec
(184) |
| 2020 |
Jan
(205) |
Feb
(287) |
Mar
(180) |
Apr
(285) |
May
(272) |
Jun
(266) |
Jul
(133) |
Aug
(253) |
Sep
(281) |
Oct
(346) |
Nov
(293) |
Dec
(253) |
| 2021 |
Jan
(218) |
Feb
(194) |
Mar
(399) |
Apr
(312) |
May
(425) |
Jun
(358) |
Jul
(160) |
Aug
(251) |
Sep
(110) |
Oct
(113) |
Nov
(257) |
Dec
(99) |
| 2022 |
Jan
(233) |
Feb
(184) |
Mar
(284) |
Apr
(221) |
May
(178) |
Jun
(231) |
Jul
(337) |
Aug
(264) |
Sep
(181) |
Oct
(183) |
Nov
(281) |
Dec
(406) |
| 2023 |
Jan
(479) |
Feb
(263) |
Mar
(278) |
Apr
(149) |
May
(186) |
Jun
(215) |
Jul
(353) |
Aug
(195) |
Sep
(232) |
Oct
(140) |
Nov
(211) |
Dec
(197) |
| 2024 |
Jan
(348) |
Feb
(167) |
Mar
(131) |
Apr
(222) |
May
(113) |
Jun
(136) |
Jul
(242) |
Aug
(105) |
Sep
(94) |
Oct
(237) |
Nov
(110) |
Dec
(155) |
| 2025 |
Jan
(372) |
Feb
(234) |
Mar
(332) |
Apr
(310) |
May
(203) |
Jun
(63) |
Jul
(193) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Viktor T. T. <vt...@vt...> - 2025-07-28 01:14:08
|
I created a branch (branch-5_48) for version 5.48. Everything seems clean at this point, testsuite (incl. share) passes with no issues I am aware of. This is the moment of built-in-pause, to see if there are any last-minute issues that may need addressing; if not, I'll complete the release tomorrow (July 28). Viktor |
|
From: Raymond T. <toy...@gm...> - 2025-07-28 00:42:52
|
On 7/27/25 3:54 PM, Raymond Toy wrote:
> On 7/27/25 12:41 PM, Jaime Villate wrote:
>
>> Hello,
>>
>> I have committed the manual.css page for the manual with a darker
>> mode that resembles the one in the Website.
> Thanks. I'll take a look at it in a bit.
Chrome Lighthouse has a few complaints:
*
[accesskey] values are not unique (for keyboard navigation)
*
html element does not have a [lang] attribute
*
Links rely on color to be distinguishable
*
Touch targets do not have sufficient size or spacing.
I think we're in pretty good shape.
Not sure about the accesskey stuff. We can add a lang attribute. Perhaps
we can underline links or something? The touch target seems to be from
the list of subsections. I'm looking at the Chap 15, Special Functions.
A bit of CSS could probably make the spacing between the itemized lists
bigger.
Same issues with dark mode.
I think we're mostly set now.
​ |
|
From: Raymond T. <toy...@gm...> - 2025-07-27 22:54:54
|
On 7/27/25 12:41 PM, Jaime Villate wrote: > Hello, > > I have committed the manual.css page for the manual with a darker mode > that resembles the one in the Website. Thanks. I'll take a look at it in a bit. > > I left the background of the examples in a darker blue, which might > contrast well with the syntax coloring that Raymond is testing; if > not, we can just leave the examples with the same color as in the > lighter theme, because I doubt that the syntax coloring scripts > support different colors for different themes. Yes and no. I just found out yesterday that currently texinfo 7.2 calls pygments with an option to inline the colors. (To prevent any collision with any class used by texinfo.) However, by default, pygments doesn't. It can even print out the CSS style that is being used. I was thinking of using some dark mode pygments style to add to our CSS file to enable dark mode for the syntax highlighting. I did a quick experiment by hacking my copy of texinfo so that it doesn't call pygments with the inline style option. This works. There is a proposal that texinfo will allow an arbitrary script to be called to do the highlighting. > > > There are three elements in the stylesheet which I have no idea what > they're used for and aren't used in any of the manual pages: > > div.textbox, div.titlebox, div.synopsisbox > > I just left them with the same colors as in the lighter theme. j A quick grep doesn't show any occurrence of textbox, titlebox, or synopsisbox in any html file. ​ |
|
From: Jaime V. <vi...@fe...> - 2025-07-27 19:41:34
|
Hello, I have committed the manual.css page for the manual with a darker mode that resembles the one in the Website. I left the background of the examples in a darker blue, which might contrast well with the syntax coloring that Raymond is testing; if not, we can just leave the examples with the same color as in the lighter theme, because I doubt that the syntax coloring scripts support different colors for different themes. There are three elements in the stylesheet which I have no idea what they're used for and aren't used in any of the manual pages: div.textbox, div.titlebox, div.synopsisbox I just left them with the same colors as in the lighter theme. Jaime |
|
From: David S. <d.s...@go...> - 2025-07-27 16:07:01
|
Thanks for implementing the Dark Theme, many eyes will be grateful! :) Raymond Toy <toy...@gm...> schrieb am So., 27. Juli 2025, 08:23: > On 7/27/25 3:14 AM, Jaime Villate wrote: > > > On 27/07/25 03:33, Raymond Toy wrote: > > BTW, > https://www.a11yproject.com/posts/using-firefox-for-accessibility-testing/#the-accessibility-tab > has a nice summary of how to use Firefox's accessibility tool. > > > Thanks for that link. It was very useful. I believe maxima.sourceforge.io > now passes all the accessibility requirements,in both light and dark themes > (at least in Firefox for Ubuntu). > > That's really fantastic! It's a small thing, except for those who could > really benefit from it. > ​ > _______________________________________________ > Maxima-discuss mailing list > Max...@li... > https://lists.sourceforge.net/lists/listinfo/maxima-discuss > |
|
From: Raymond T. <toy...@gm...> - 2025-07-27 15:17:22
|
On 7/27/25 3:14 AM, Jaime Villate wrote: > > On 27/07/25 03:33, Raymond Toy wrote: >> BTW, >> https://www.a11yproject.com/posts/using-firefox-for-accessibility-testing/#the-accessibility-tab >> has a nice summary of how to use Firefox's accessibility tool. > > Thanks for that link. It was very useful. I believe > maxima.sourceforge.io now passes all the accessibility requirements,in > both light and dark themes (at least in Firefox for Ubuntu). That's really fantastic! It's a small thing, except for those who could really benefit from it. ​ |
|
From: Daniel V. <dan...@ya...> - 2025-07-27 10:51:10
|
Thank you, Viktor,
Daniel Volinski
En domingo, 27 de julio de 2025, 11:50:02 GMT+3, Viktor T. Toth <vt...@vt...> escribió:
Dear Daniel,
I cannot tell with certainty if what you did is correct, but it looks like you did everything by the book and got a sensible result; I don't see any obvious red flags. You used itensor/ctensor as intended, in a neat way: Found an itensor expression that could be correctly evaluated, converted it to ctensor, and then assigned values to what are normally itensor objects (ifg/ifr/ifri) but that's quite alright, since you were no longer using itensor at this point, you just wanted to evaluate the matrix terms in your SC. Your \omega appeared rather sparse but then again, that seems to be expected given that you only have time dependence, no dependence on the other coordinates. In short, I *think* you got it right, just don't quote me on this please :-)
Viktor
On 7/26/2025 6:52 AM, Daniel Volinski via Maxima-discuss wrote:
Hi Viktor,
I was thinking about calculating the spin connector tensor the following way: I'm using the formula for the spin connection from: Sean Carroll, Spacetime and Geometry, Appendix J, Noncoordinate Bases Equation J.21, Page 483.
load(itensor)$
load(ctensor)$
iframe_flag:true$ cframe_flag:true$ ct_coords:[t,x,y,z]$
dim:length(ct_coords)$
depends(a,t)$
ishow(Eq:ω([μ,-a,b])=T([ν,-a])*S([-λ,b])*'icc2([μ,λ],[ν])- S([-λ,b])*idiff(T([λ,-a]),μ))$ Eq:contract(canform(ev(Eq,icc2,ifc2,ifc1,ifb)))$
SC:ic_convert(Eq)$
lfg:matrix([-1,0,0,0],[0,1,0,0],[0,0,1,0],[0,0,0,1])$
fri:matrix([1,0,0,0],[0,a,0,0],[0,0,a,0],[0,0,0,a])$
cmetric()$
depends([ifg,ifr,ifri],ct_coords)$
ifg:ident(dim)$ ifr:fr$ifri:fri$ array(ω,dim,dim,dim)$ S:fr$T:fri$ ev(SC)$
genmatrix(lambda([i,j],ω[1,i,j]),dim,dim);
cdisplay(ω,1)$
Is that correct? Thanks,
Daniel Volinski
En domingo, 20 de julio de 2025, 17:04:23 GMT+3, Daniel Volinski via Maxima-discuss <max...@li...> escribió:
Hi Viktor,
Thank you for your input, comments and suggestions, very helpful.
What I was planning to do is to use the spin connection to calculate other things like curvature tensor, Ricci scalar, although there are other ways to calculate them. Eventually, I was planning to branch into Cartan's structure equation.
Daniel Volinski
En domingo, 20 de julio de 2025, 11:43:21 GMT+3, Viktor T. Toth <vt...@vt...> escribió:
Well, it is certainly possible to do the basics, but I think the real question is, what exactly do you want to do?
In itensor, for instance, we could do this:
load(itensor)$
imetric(g)$
defcon(e,h,e)$
components(g([m,n],[]),e([m],[a])*e([n],[b])*h([a,b],[]))$
components(w([m],[a,b]),e([n],[a])*'ichr2([s,m],[n])*e([],[s,b])+e([n],[a])*e([],[n,b],m))$
declare(h,constant)$
ishow(w([m],[a,b]))$
or even this:
ishow(rename(%,100))$
ishow(ev(%,ichr2))$
ishow(contract(rename(expand(%))))$
but it's not exactly useful. Also, unless we are very careful, itensor gets easily confused when it comes to terms that have different raising/lowering rules for various indices.
The ctensor package does have some support for a tetrad base. Run demo(tetrad), for instance, or also demo(ctensor4). There's also some support in itensor; try demo(itensor9). These might prove useful, depending on what you are trying to do.
Eons ago, I also tried to document some of what is implemented in a preprint, at https://arxiv.org/pdf/cs/0503073 . Does not directly answer your question but it might help explore the implemented capabilities in these two packages.
Viktor
On 7/19/2025 3:40 PM, Daniel Volinski via Maxima-discuss wrote:
Hi All,
I would like to calculate the Spin connection - Wikipedia using itensor/ctensor packages. Given a metric, is there any way to calculate it, or maybe it is some of the variables that already exist in the packages under some different name.
Thanks,
Daniel Volinski
_______________________________________________
Maxima-discuss mailing list
Max...@li...
https://lists.sourceforge.net/lists/listinfo/maxima-discuss
_______________________________________________
Maxima-discuss mailing list
Max...@li...
https://lists.sourceforge.net/lists/listinfo/maxima-discuss
_______________________________________________
Maxima-discuss mailing list
Max...@li...
https://lists.sourceforge.net/lists/listinfo/maxima-discuss
|
|
From: Jaime V. <vi...@fe...> - 2025-07-27 10:23:55
|
On 27/07/25 11:11, Jaime Villate via Maxima-discuss wrote: > "The source code is not yet on GitHub, since traces of non-public > source are still being removed. However, a copy of the executable for > Windows, version 6.1.2, is now posted on > https://github.com/ScientificWord/sciword. The instructions for > installing it on Windows are:..." Actually, that paragraph is now obsolete. The whole code seems to be available with a Mozilla license, which is fine with me. But I still have the big limitation that its source code is Swahili to me. Jaime |
|
From: Jaime V. <vi...@fe...> - 2025-07-27 10:15:09
|
On 27/07/25 03:33, Raymond Toy wrote: > BTW, > https://www.a11yproject.com/posts/using-firefox-for-accessibility-testing/#the-accessibility-tab > has a nice summary of how to use Firefox's accessibility tool. Thanks for that link. It was very useful. I believe maxima.sourceforge.io now passes all the accessibility requirements,in both light and dark themes (at least in Firefox for Ubuntu). Regards, Jaime |
|
From: Jaime V. <vi...@fe...> - 2025-07-27 10:12:12
|
On 26/07/25 18:49, - wrote: > Scientific Word was released as open source on Github > (https://github.com/ScientificWord/sciword, > https://mackichan.com/techtalk/v60/FreeSW.htm). Hello frifor, Thank you for the information. It looks very interesting. I personally have two problems: "The source code is not yet on GitHub, since traces of non-public source are still being removed. However, a copy of the executable for Windows, version 6.1.2, is now posted on https://github.com/ScientificWord/sciword. The instructions for installing it on Windows are:..." 1. I don't do any programming in Windows. I prefer to work in LInux and then create a version for Windows, from Linux, by using Wine (actually, I wait for Wolfgang Dauterman to do it and then go and check his result in a Windows machine!). 2. I would rather wait until the complete code is released as free software. In the meantime, I are lots of ideas in their interface which I could use and implement in Xmaxima (my biggest limitation with Xmaxima is lack of time and not any limitations of Tcl/Tk). Of course, it would be very nice if other programmers with different background from mine jump in and start making it work with Maxima instead of Mupad. Regards, Jaime |
|
From: Viktor T. T. <vt...@vt...> - 2025-07-27 08:50:01
|
Dear Daniel, I cannot tell with certainty if what you did is correct, but it looks like you did everything by the book and got a sensible result; I don't see any obvious red flags. You used itensor/ctensor as intended, in a neat way: Found an itensor expression that could be correctly evaluated, converted it to ctensor, and then assigned values to what are normally itensor objects (ifg/ifr/ifri) but that's quite alright, since you were no longer using itensor at this point, you just wanted to evaluate the matrix terms in your SC. Your \omega appeared rather sparse but then again, that seems to be expected given that you only have time dependence, no dependence on the other coordinates. In short, I *think* you got it right, just don't quote me on this please :-) Viktor On 7/26/2025 6:52 AM, Daniel Volinski via Maxima-discuss wrote: > Hi Viktor, > > I was thinking about calculating the spin connector tensor the > following way: > I'm using the formula for the spin connection from: > Sean Carroll, Spacetime and Geometry, Appendix J, Noncoordinate Bases > Equation J.21, Page 483. > > load(itensor)$ > load(ctensor)$ > iframe_flag:true$ > cframe_flag:true$ > ct_coords:[t,x,y,z]$ > dim:length(ct_coords)$ > depends(a,t)$ > ishow(Eq:ω([μ,-a,b])=T([ν,-a])*S([-λ,b])*'icc2([μ,λ],[ν])- > S([-λ,b])*idiff(T([λ,-a]),μ))$ > Eq:contract(canform(ev(Eq,icc2,ifc2,ifc1,ifb)))$ > SC:ic_convert(Eq)$ > lfg:matrix([-1,0,0,0],[0,1,0,0],[0,0,1,0],[0,0,0,1])$ > fri:matrix([1,0,0,0],[0,a,0,0],[0,0,a,0],[0,0,0,a])$ > cmetric()$ > depends([ifg,ifr,ifri],ct_coords)$ > ifg:ident(dim)$ > ifr:fr$ifri:fri$ > array(ω,dim,dim,dim)$ > S:fr$T:fri$ > ev(SC)$ > genmatrix(lambda([i,j],ω[1,i,j]),dim,dim); > cdisplay(ω,1)$ > > Is that correct? > Thanks, > > Daniel Volinski > > > En domingo, 20 de julio de 2025, 17:04:23 GMT+3, Daniel Volinski via > Maxima-discuss <max...@li...> escribió: > > > Hi Viktor, > > Thank you for your input, comments and suggestions, very helpful. > > What I was planning to do is to use the spin connection to calculate > other things like curvature tensor, Ricci scalar, although there are other > ways to calculate them. Eventually, I was planning to branch into > Cartan's structure equation. > > Daniel Volinski > > > En domingo, 20 de julio de 2025, 11:43:21 GMT+3, Viktor T. Toth > <vt...@vt...> escribió: > > > Well, it is certainly possible to do the basics, but I think the real > question is, what exactly do you want to do? > > In itensor, for instance, we could do this: > > load(itensor)$ > imetric(g)$ > defcon(e,h,e)$ > components(g([m,n],[]),e([m],[a])*e([n],[b])*h([a,b],[]))$ > components(w([m],[a,b]),e([n],[a])*'ichr2([s,m],[n])*e([],[s,b])+e([n],[a])*e([],[n,b],m))$ > declare(h,constant)$ > ishow(w([m],[a,b]))$ > > or even this: > > ishow(rename(%,100))$ > ishow(ev(%,ichr2))$ > ishow(contract(rename(expand(%))))$ > > but it's not exactly useful. Also, unless we are very careful, itensor > gets easily confused when it comes to terms that have different > raising/lowering rules for various indices. > > The ctensor package does have some support for a tetrad base. Run > demo(tetrad), for instance, or also demo(ctensor4). There's also some > support in itensor; try demo(itensor9). These might prove useful, > depending on what you are trying to do. > > Eons ago, I also tried to document some of what is implemented in a > preprint, at https://arxiv.org/pdf/cs/0503073 > <https://arxiv.org/pdf/cs/0503073> . Does not directly answer your > question but it might help explore the implemented capabilities in > these two packages. > > > Viktor > > > > On 7/19/2025 3:40 PM, Daniel Volinski via Maxima-discuss wrote: > Hi All, > > I would like to calculate the Spin connection - Wikipedia > <https://en.wikipedia.org/wiki/Spin_connection> using itensor/ctensor > packages. > Given a metric, is there any way to calculate it, or maybe it is some > of the variables that > already exist in the packages under some different name. > > Thanks, > > Daniel Volinski > > > > > _______________________________________________ > Maxima-discuss mailing list > Max...@li... <mailto:Max...@li...> > https://lists.sourceforge.net/lists/listinfo/maxima-discuss <https://lists.sourceforge.net/lists/listinfo/maxima-discuss> > _______________________________________________ > Maxima-discuss mailing list > Max...@li... > https://lists.sourceforge.net/lists/listinfo/maxima-discuss > > > _______________________________________________ > Maxima-discuss mailing list > Max...@li... > https://lists.sourceforge.net/lists/listinfo/maxima-discuss |
|
From: Raymond T. <toy...@gm...> - 2025-07-27 02:33:37
|
On 7/26/25 7:09 PM, Raymond Toy wrote: > On 7/26/25 2:47 PM, Jaime Villate wrote: > >> >> On 26/07/25 22:21, Raymond Toy wrote: >>> >>> That's fine with me. Lighthouse does complain about lack of contrast >>> and link coloring, though. We might want to update these. Someday. >>> >> How about the new version of the Website that I submitted today, does >> it still complain? >> > If you mean dark mode for maxima.sourceforge.io/lisp.html, lighthouse > says the only issue is that there's not enough contrast between > foreground and background. Some of the entries mentioned: > > * > > "A Computer Algebra System" on the dark gray background > > * > > All of the main text on the gray background > > * > > Basically all of the blue links > > * > > All of the inline code elements like |(to-maxima)| > > There are others but they all seem to be variations of the above. > > I do not know if any of the common styles like Github dark will pass > the accessibility tests. https://pygments.org/styles/ lists some > styles with high contrast, including github dark, although I find any > kind of reddish color on the black background rather hard to see. > BTW, https://www.a11yproject.com/posts/using-firefox-for-accessibility-testing/#the-accessibility-tab has a nice summary of how to use Firefox's accessibility tool. > ​ > > > _______________________________________________ > Maxima-discuss mailing list > Max...@li... > https://lists.sourceforge.net/lists/listinfo/maxima-discuss ​ |
|
From: Raymond T. <toy...@gm...> - 2025-07-27 02:09:25
|
On 7/26/25 2:47 PM, Jaime Villate wrote: > > On 26/07/25 22:21, Raymond Toy wrote: >> >> That's fine with me. Lighthouse does complain about lack of contrast >> and link coloring, though. We might want to update these. Someday. >> > How about the new version of the Website that I submitted today, does > it still complain? > If you mean dark mode for maxima.sourceforge.io/lisp.html, lighthouse says the only issue is that there's not enough contrast between foreground and background. Some of the entries mentioned: * "A Computer Algebra System" on the dark gray background * All of the main text on the gray background * Basically all of the blue links * All of the inline code elements like |(to-maxima)| There are others but they all seem to be variations of the above. I do not know if any of the common styles like Github dark will pass the accessibility tests. https://pygments.org/styles/ lists some styles with high contrast, including github dark, although I find any kind of reddish color on the black background rather hard to see. ​ |
|
From: Jaime V. <vi...@fe...> - 2025-07-26 21:47:42
|
On 26/07/25 22:21, Raymond Toy wrote: > > That's fine with me. Lighthouse does complain about lack of contrast > and link coloring, though. We might want to update these. Someday. > How about the new version of the Website that I submitted today, does it still complain? Jaime > ​ |
|
From: Raymond T. <toy...@gm...> - 2025-07-26 21:25:36
|
On 7/26/25 12:49 PM, Jaime Villate wrote: > Hello Raymond, > > I have noticed that the index.html page looks very different when > produced with texinfo 6.8 or 7.2, as you can see in the attachments. > > With version 6.8 the page has a title and it shows just the detailed > table of contents. When you click on a line in that table, it takes > you directly to the page for that topic. > > Using version 7.2 there is no tile, and there is a "short" table of > contents followed by the detailed table of contents. When one clicks > on the topics of the short table of contents, it moves down the page > to the same topic in the detailed table of contents. > > Would it be possible to make texinfo 7.2 produce the same result as > texinfo 6.8? I'll look into it. I'm not sure why there's a difference. Maybe 6.8 doesn't recognize @summarycontents? I seem to remember that sometimes it puts that at the end of the output, which always struck me as very odd. Or maybe that was TeX? In any case, I'll check since I have both versions around. ​ |
|
From: Raymond T. <toy...@gm...> - 2025-07-26 21:21:38
|
On 7/26/25 10:53 AM, Jaime Villate wrote: > On 26/07/25 16:15, Raymond Toy wrote: >> A standard theme is probably a good idea. But it will probably make >> the manual look quite a bit different from before. I think that’s ok, >> if the colors look good. > > I'm only changing the colors of the darker theme until we find > something we like. No need to change the lighter theme. That's fine with me. Lighthouse does complain about lack of contrast and link coloring, though. We might want to update these. Someday. ​ |
|
From: Jaime V. <vi...@fe...> - 2025-07-26 19:49:16
|
Hello Raymond, I have noticed that the index.html page looks very different when produced with texinfo 6.8 or 7.2, as you can see in the attachments. With version 6.8 the page has a title and it shows just the detailed table of contents. When you click on a line in that table, it takes you directly to the page for that topic. Using version 7.2 there is no tile, and there is a "short" table of contents followed by the detailed table of contents. When one clicks on the topics of the short table of contents, it moves down the page to the same topic in the detailed table of contents. Would it be possible to make texinfo 7.2 produce the same result as texinfo 6.8? Jaime |
|
From: Jaime V. <vi...@fe...> - 2025-07-26 17:53:47
|
On 26/07/25 16:15, Raymond Toy wrote: > A standard theme is probably a good idea. But it will probably make > the manual look quite a bit different from before. I think that’s ok, > if the colors look good. I'm only changing the colors of the darker theme until we find something we like. No need to change the lighter theme. Jaime |
|
From: - <fr...@po...> - 2025-07-26 17:50:01
|
Hello, I would like to suggest using Scientific Word as an user interface for Maxima. MacKichan Software distributed three program versions: Scientific Word, Scientific Notebook, and Scientific Workplace until 2021 (see https://en.wikipedia.org/wiki/Scientific_WorkPlace). With Scientific Word, LateX can be written as WYSIWYG (https://www.hallogram.com/scientificword/). With Scientific Workplace, LateX can be written as WYSIWYG AND calculated simultaneously via an interface to MuPad and Maple (https://www.hallogram.com/scientificworkplace/index/). With Scientific Notebook, text can be written as WYSIWYG AND calculated simultaneously via an interface to MuPad or Maple, but the document cannot be saved in LateX format (https://www.hallogram.com/scientificnote/). I have worked as an engineer with Scientific Workplace and Scientific Notebook for almost 30 years. I have also worked with Derive, Mathematica, Maple, and MathCAD. In my opinion, Scientific Notebook and Scientific Workplace are the best programs for engineers to perform calculations and document them neatly at the same time: easy writing like in Word, in-line calculations, use of units, and attractive layout. You don't need to know the syntax for MuPad and Maple. Most commands are available by the menu and short-cuts. Appending to this email are some screenshots of Scientific Notebook 4.1. The manual for Scientific Notebook / Scientific Workplace can be found here: https://s3-us-west-2.amazonaws.com/mackichan-com-ftp/pub/download/version60/doingmath-60.pdf. Scientific Workplace is superior to Scientific Notebook for scientific publications because it can save files in LateX format. In my opinion, these programs are the perfect user interface for computer algebra systems. Unfortunately, Scientific Notebook and Scientific Workplace are no longer being developed. Scientific Word was released as open source on Github (https://github.com/ScientificWord/sciword, https://mackichan.com/techtalk/v60/FreeSW.htm). I asked MacKichan whether Scientific Notebook or Scientific Workplace could be released as source code so that it would be possible to create an interface to Maxima. MacKichan replied that the open source project Scientific Word 6 can be found on GitHub and includes basically the code for Scientific WorkPlace with the MuPad components and some of the MuPad-specific glue code removed. MacKichan says, it is feasible to replace it with another computer algebra system. (MacKichan thinks that the SageMath project would be the easiest, but unfortunately there has been little activity in that project.) I myself cannot program. But if any of you could reprogram the interface in Scientific Word 6 from Maple/MuPad to Maxima, we would have the best user interface for a computer algebra system, and it would be open source too. That would be truly valuable work that would benefit many people, especially students, engineers, and scientists. Please consider whether you would like to implement this. Best regards frifor |
|
From: Raymond T. <toy...@gm...> - 2025-07-26 15:16:13
|
On 7/26/25 3:19 AM, Jaime Villate wrote: > On 25/07/25 23:41, Raymond Toy wrote: >> Chrome's Lighthouse tool has an accessibility tool. If we're going to >> start changing colors and such, perhaps we should use that to make >> sure we have sufficient contrast. Currently, with the standard light >> mode, we don't have enough contrast in many elements and links are >> only distinguishable by color, which I guess is not a good for >> accessibility. I have noticed this before---visited links are a light >> blue that is sometimes hard to notice. > > I don't use Chrome in Ubuntu (might have in Wndows; will have to > check). Another idea I just had is to use a color palette from a > standard theme (Tango, Gnome, Solarized, Ubuntu, etc) instead of > trying to reinvent the wheel. I will give it a try. I almost always use Firefox, which also has some kind of accessibility tool, but I didn’t understand what it was telling me so I tried Chrome instead. A standard theme is probably a good idea. But it will probably make the manual look quite a bit different from before. I think that’s ok, if the colors look good. ​ |
|
From: Daniel V. <dan...@ya...> - 2025-07-26 11:13:31
|
Hi Viktor,
I was thinking about calculating the spin connector tensor the following way:I'm using the formula for the spin connection from:Sean Carroll, Spacetime and Geometry, Appendix J, Noncoordinate BasesEquation J.21, Page 483.
load(itensor)$
load(ctensor)$
iframe_flag:true$cframe_flag:true$ct_coords:[t,x,y,z]$
dim:length(ct_coords)$
depends(a,t)$
ishow(Eq:ω([μ,-a,b])=T([ν,-a])*S([-λ,b])*'icc2([μ,λ],[ν])- S([-λ,b])*idiff(T([λ,-a]),μ))$Eq:contract(canform(ev(Eq,icc2,ifc2,ifc1,ifb)))$
SC:ic_convert(Eq)$
lfg:matrix([-1,0,0,0],[0,1,0,0],[0,0,1,0],[0,0,0,1])$
fri:matrix([1,0,0,0],[0,a,0,0],[0,0,a,0],[0,0,0,a])$
cmetric()$
depends([ifg,ifr,ifri],ct_coords)$
ifg:ident(dim)$ifr:fr$ifri:fri$array(ω,dim,dim,dim)$S:fr$T:fri$ev(SC)$
genmatrix(lambda([i,j],ω[1,i,j]),dim,dim);
cdisplay(ω,1)$
Is that correct?Thanks,
Daniel Volinski
En domingo, 20 de julio de 2025, 17:04:23 GMT+3, Daniel Volinski via Maxima-discuss <max...@li...> escribió:
Hi Viktor,
Thank you for your input, comments and suggestions, very helpful.
What I was planning to do is to use the spin connection to calculateother things like curvature tensor, Ricci scalar, although there are otherways to calculate them. Eventually, I was planning to branch intoCartan's structure equation.
Daniel Volinski
En domingo, 20 de julio de 2025, 11:43:21 GMT+3, Viktor T. Toth <vt...@vt...> escribió:
Well, it is certainly possible to do the basics, but I think the real question is, what exactly do you want to do?
In itensor, for instance, we could do this:
load(itensor)$
imetric(g)$
defcon(e,h,e)$
components(g([m,n],[]),e([m],[a])*e([n],[b])*h([a,b],[]))$
components(w([m],[a,b]),e([n],[a])*'ichr2([s,m],[n])*e([],[s,b])+e([n],[a])*e([],[n,b],m))$
declare(h,constant)$
ishow(w([m],[a,b]))$
or even this:
ishow(rename(%,100))$
ishow(ev(%,ichr2))$
ishow(contract(rename(expand(%))))$
but it's not exactly useful. Also, unless we are very careful, itensor gets easily confused when it comes to terms that have different raising/lowering rules for various indices.
The ctensor package does have some support for a tetrad base. Run demo(tetrad), for instance, or also demo(ctensor4). There's also some support in itensor; try demo(itensor9). These might prove useful, depending on what you are trying to do.
Eons ago, I also tried to document some of what is implemented in a preprint, at https://arxiv.org/pdf/cs/0503073 . Does not directly answer your question but it might help explore the implemented capabilities in these two packages.
Viktor
On 7/19/2025 3:40 PM, Daniel Volinski via Maxima-discuss wrote:
Hi All,
I would like to calculate the Spin connection - Wikipedia using itensor/ctensor packages. Given a metric, is there any way to calculate it, or maybe it is some of the variables that already exist in the packages under some different name.
Thanks,
Daniel Volinski
_______________________________________________
Maxima-discuss mailing list
Max...@li...
https://lists.sourceforge.net/lists/listinfo/maxima-discuss
_______________________________________________
Maxima-discuss mailing list
Max...@li...
https://lists.sourceforge.net/lists/listinfo/maxima-discuss
|
|
From: Jaime V. <vi...@fe...> - 2025-07-26 10:19:36
|
On 25/07/25 23:41, Raymond Toy wrote: > Chrome's Lighthouse tool has an accessibility tool. If we're going to > start changing colors and such, perhaps we should use that to make > sure we have sufficient contrast. Currently, with the standard light > mode, we don't have enough contrast in many elements and links are > only distinguishable by color, which I guess is not a good for > accessibility. I have noticed this before---visited links are a light > blue that is sometimes hard to notice. I don't use Chrome in Ubuntu (might have in Wndows; will have to check). Another idea I just had is to use a color palette from a standard theme (Tango, Gnome, Solarized, Ubuntu, etc) instead of trying to reinvent the wheel. I will give it a try. Jaime |
|
From: Raymond T. <toy...@gm...> - 2025-07-25 22:41:17
|
On 7/25/25 2:09 PM, Jaime Villate wrote: > On 25/07/25 21:09, Raymond Toy wrote: >> I copied the changes over to manual.css. A few comments. Don't you >> need to set the text color? For me, it's still black, so really hard >> to see. I just set it to white. I think the link color needs to >> change too; it's really hard to see on the dark gray background. > > I did set it to a very light gray, as yon can see in > https://maxima.sourceforge.io/ That looks fine. > > And then in https://maxima.sourceforge.io/lisp.html you can see my > proposal for an example box with syntax coloring. This is really hard for me to read. The read is unreadable. The contrast between the blue input line and the background is also hard to read. Chrome's Lighthouse tool has an accessibility tool. If we're going to start changing colors and such, perhaps we should use that to make sure we have sufficient contrast. Currently, with the standard light mode, we don't have enough contrast in many elements and links are only distinguishable by color, which I guess is not a good for accessibility. I have noticed this before---visited links are a light blue that is sometimes hard to notice. > > Regards, > > Jaime > ​ |
|
From: Jaime V. <vi...@fe...> - 2025-07-25 21:09:40
|
On 25/07/25 21:09, Raymond Toy wrote: > I copied the changes over to manual.css. A few comments. Don't you > need to set the text color? For me, it's still black, so really hard > to see. I just set it to white. I think the link color needs to change > too; it's really hard to see on the dark gray background. I did set it to a very light gray, as yon can see in https://maxima.sourceforge.io/ And then in https://maxima.sourceforge.io/lisp.html you can see my proposal for an example box with syntax coloring. Regards, Jaime |
|
From: Raymond T. <toy...@gm...> - 2025-07-25 20:09:16
|
On 7/25/25 12:23 PM, Jaime Villate wrote: > That's because I did the change in the Website and not in the manual. > The website already has the dark option, but Sourceforge still doesn't > show it (it takes at least 30 minutes for the update). Once we are > happy with the color scheme I will just copy it to the Manual. > I copied the changes over to manual.css. A few comments. Don't you need to set the text color? For me, it's still black, so really hard to see. I just set it to white. I think the link color needs to change too; it's really hard to see on the dark gray background. Other than that, I think it looks pretty good, even with pygments highlighting enabled. But I never use dark mode. ​ |
63 messages has been excluded from this view by a project administrator.
