raptop changed the topic of #kspacademia to: https://gist.github.com/pdn4kd/164b9b85435d87afbec0c3a7e69d3e6d | Dogs are cats. Spiders are cat interferometers. | Космизм сегодня! | Document well, for tomorrow you may get mauled by a ネコバス. | <UmbralRaptor> egg|nomz|egg: generally if your eyes are dewing over, that's not the weather. | <ferram4> I shall beat my problems to death with an engineer. | We can haz pdf
e_14159 has quit [Ping timeout: 190 seconds]
e_14159 has joined #kspacademia
egg|cell|egg has quit [Ping timeout: 198 seconds]
egg|cell|egg has joined #kspacademia
<bofh>
hrm
<bofh>
I need a copy of "Inscriptions antiques de musée de la ville de Lyon"
<oeuf>
bofh: however have you considered: the number of comment records,
<bofh>
oeuf: yes, definetly,
<bofh>
also man i miss being able to just walk over to the BNF
* bofh
stares forlornly at calendar... 3 and a bit more months >_<
<oeuf>
bofh: "Although the number of comment records is theoretically unlimited, users are asked to practice constraint. It was considered to limit the number of comment lines to 40 or 400. However, any such limit would seem somewhat arbitrary. The beauty of the SP3 format is really its compactness, and it would seem to go against the spirit of SP3 to see a file with tens of thousands of comment lines and only 3,200 lines of
<oeuf>
actual data. Please make your comments brief."
<oeuf>
(SP3-d specification)
<bofh>
LOL
<bofh>
I am now imagining an SP3-d file where the comments section is an XML schema encoding a blob of the SPICE kernel for the relevant object.
<oeuf>
SP3-c and earlier have exactly 4 comment lines, with SP3-d the number of comment records is unlimited
<bofh>
Yes, which is why i specified SP3-d,
egg|cell|egg has quit [Ping timeout: 190 seconds]
egg|cell|egg has joined #kspacademia
egg|cell|egg has quit [Ping timeout: 183 seconds]
egg|cell|egg has joined #kspacademia
egg|cell|egg has quit [Read error: -0x1: UNKNOWN ERROR CODE (0001)]
egg|cell|egg has joined #kspacademia
<oeuf>
bofh: gah, does anybody know how to write SP3 files
<oeuf>
the IDS uses m/s instead of dm/s, the ILRS uses %/* for comments instead of /*
egg|cell|egg has quit [Ping timeout: 189 seconds]
egg|cell|egg has joined #kspacademia
egg|cell|egg has quit [Ping timeout: 180 seconds]
egg|cell|egg has joined #kspacademia
egg|cell|egg has quit [Ping timeout: 202 seconds]
egg|cell|egg has joined #kspacademia
<SnoopJeDi>
...huh. I did not realize this, but the GOES sats actually do a good bit of solar science. Neat!
Moistmelon has joined #kspacademia
<UmbralRaptor>
nice
<UmbralRaptor>
… if I revolve an eevee, does it turn into a napoleon?
<SnoopJeDi>
reevolution
<UmbralRaptor>
Anyway, I managed to kill our cluster
<bofh>
UmbralRaptor: LOL at the reevelution, yikes at killing the cluster (how did that happen, anyhow?)
<bofh>
SnoopJeDi: yep!
<bofh>
irritatingly the solar science data is only in the high-bandwidth GRB feed, which means I haven't been able to downlink it yet. >_<
<UmbralRaptor>
bofh: it's not dead dead, but remote access is
<bofh>
oeuf: admittedly, dm/s is a fucking weird unit
<UmbralRaptor>
sudo ufw enable
<SnoopJeDi>
someone in another channel trotted out the question of "would a flare produce a modulation in ground detection of muons"
<bofh>
uhm
<bofh>
oops
<SnoopJeDi>
and in the course of trying to find the info for that, I stumbled into GOES solar stuff. What a delightful surprise
<UmbralRaptor>
trying to figure out why port forwarding is enabled on the head node, but the rest can't see the outside world (so they can't use eg: apt-get)