kurja

Send a probe? Really now.

Looks like there are quite few and blurry stars in the frame, DSS might not find enough of them to align with. I don't really use DSS... Maybe you could try something like this http://ukastroimaging.co.uk/forums/index.php?topic=30566.0

just use body:mu in your equation?

Asking again does not change the answer you really do need multiple lights, tweaking a bunch of copies isn't going to do what you want. And sorry about the weird quotes, again, forum ui on mobile is rather horrible

A thought: if you harvest ore and recover at KSC, do you profit?

Although if you're looking at single exposures, can you really tell if it's thermal noise, which appears in a static pattern and can be helped with darks, or if it's shot noise, which is random and can be helped by integrating more lights? I haven't really seen what would clearly be thermal noise from any dslr cmos, but then again I only do astrophoto when it's cold outside. On another forum I saw a rather thorough test, result was that noise increases steeply after cmos sensor temperature exceeds 0C and it warms up by about 10C during continuous use... So -10C or below, and we should be good to go

Ah, your warmer conditions may play a part here, I'm at >60 latitude so summer time is no-no for astrophoto and the temperatute on clear winter nights is pretty much always quite far in the negative degrees.

Have you compared a same set of lights with and without darks? I never saw any benefit so I just don't bother with darks, I just use flats, and bias because flats don't come out right unless adjusted for bias. I use pixinsight, it can save in fits too, I usually save my "final iteration" in 16b tiff though. My tracking is never spot on anyway, so as the images are aligned before integrating, bad pixels and such sensor problems get solved as a free bonus Maybe darks help if your tracking is pixel perfect, but who has that kind of tracking and shoots with a normal camera...

I'm not so sure, a goto mount will point which ever way you tell it to - why not at a satellite? https://www.youtube.com/watch?v=Mi9ZOiaLKxc

Stacking copies of one picture is not helpful as the whole point of it is to avarage out random variations. I find dark frames are quite useless with dslr cameras, as raw from them isn't genuinely raw; calibration doesn't quite work like it should. Light pollution does not increase noise, it usually just introduces a gradient or drowns out your signal. Calibrating your lights does not help, but there are processing options; search for gradient removal and/or background extraction. Some filters may be of help when taking the lights. (sorry about the broken quote, stupid phone...)

I intended to respond to flight at karman line, my mistake as you can see, but anyway buoancy should be much greater if in a tin atmosphere ,) Semantics.

...A balloon filled with vacuum would be buoyant in vacuum? Maybe not ,)

Would the plushies survive a freefall to the moon?

Except that they weren't? No other aircraft flew with those engines. Design was based on military use engines though.

So you guys dive really well.

Yet it landed on someone's yard? It's an awesome project, but seriously, do look into what your local legislation has to say about building and launching rockets.

Staging to a final monoprop stage ofc changes things, but if that's the case, in KSP you get more dv in that stage (AND less weight!) with liquid fuel and a pair of spider engines. Just did some back of the envelope calculations and I ended up with a ~60 m/s advantage using spiders versus 2 of 4 way rcs consuming ~300kg of propellant (smallest inline monoprop tank or a toroidal lf/ox tank) added to a 2 ton pod. Sometimes one wants to have monoprop, for docking maybe, but strictly looking at delta v, I can't think of a case where monoprop would be better? Could you give an example? Hmm if you only have rcs fuel in a pod so you get that tank mass "for free"...? Edit - with adding only rcs blocks the added weight is not much, but still, the dv to be had from the 10 units of fuel in a small pod only amounts to ~40m/s for a two ton craft. Pretty sure the total dv will be higher if omitting rcs and monoprop, than by adding rcs to use those 10 units in a capsule.

Ah. My old pocket calculator that I've used since my school years has a "log" button that defaults to base 10 - and a separate "ln" button. So, all this time I've assumed that log is base ten unless specified otherwise Edit - I believe ms excel, and most other spreadsheets too, behave similarly.

Is "log" here same as ln??

Looking only at delta v, it's always beneficial to spend the lower isp propellant first.

I saw this behavior in 100% stock game with a probe near the sun, it would heat up during time warp and then cool down when I cancelled warp.

I'll try a practical example: since dv = Isp*g0 ln(m_full/m_empty) In flight, right click the engine in your current stage and it will display the Isp (specific impulse). Then right click your tanks that are feeding that engine to see how much fuel they have left. We need one more thing: hit 'm' to go to map view, and click the little 'i' button; the information box tells you your vessel's total mass. Now we have all the information you need Let's say your total mass is 5 tons, you have 180lf and 220ox, and your Isp is 320. So, the calculation: in KSP, liquid fuel and oxidizer both weigh 5kg per unit. So if you have 180 units of fuel and 220 units of oxidizer, mass of your fuel is (220+180) * 5kg = 2000kg Divide your total mass, five tons, with your total mass minus the fuel's mass; 5000 / (5000 - 2000) = 1.666... Next find that 'ln' button on your calculator (or put =ln(1.666) in a spreadsheet) for ln(1.66) = 0.5108... That is the number you need to multiply with specific impulse and g, so 9.81 * 320 * 0.5108 = 1604 m/s hope that helps

Pretty sure an/dn markers have ever existed only when a target has been selected. I'm afraid that's not what an and dn mean.

It's an OSC camera? Your picture looks like it hasn't been debayered / demosaiced; you need to do that to the raw data of your image before it can be viewed in color. An auto-processed (color) thumbnail or is sometimes available and some programs also auto-process raws for preview, which might confuse things at first. Usual work order is to calibrate with raw, demosaic, then align and integrate. Sorry if this was a stupid comment, but to my eye your picture looks exactly like what I'd expect an un-debayered image to look like.

Hm now that I think of it wasn't that the default behavior in earlier versions?