Peter Teuben
Peter Teuben
It seems ".ta +1.25i +4.5i" is a better default for the output PDF, but tight for terminals.
Another new formatting idea is to put ".br" before the default. But now we have several ways how to write the default: ``` [Default: 1.0] [1.0] Default: 1.0 default: 1.0...
case in point: Fedora40 ships with gcc-14 and it has several failures in NEMO due to "bad" old habits. They do already show up as warnings (-W...) in earlier versions...
this could also be a more conservative setting of the cpu freqs..... laptops are just terrible to use for benchmarking. As a new kubuntu was installed, one never knows how...
The ones important to fix for casa are: TELESCOP, CUNIT, RESTFREQ
Near line 880 in getparam.c the defined(linux) code will need to be invalidated.
Better example is; dumbp < $NEMO/data/starlab/cube10.dyn | tabcols - > cube10.col tabtos cube10.col cube10.dat block1=mass,pos,vel times=0 this avoid shortcomings in both tabcomment and tabtos (which should be fixed)
In discussions with a colleagues, I was given this link, of somebody who used github to manage their experiments (in MESA) : https://github.com/adamjermyn/remote_experiments
Since I don't recall where my /usr/local/lib/libcasa* came from, I could imagine it was build when my $PATH included miniconda.... Since I can fix this by disabling miniconda, i'm ok...
i guess automatic branch creation doesn't exist here, but I'll use the branch number notation to refer to the branch in my fork