More stuff

Text:
Results
-Ion production and direct heating - needs results
-Chemistry (further)? - needs results
-Heating (further - Joule heating etc)? - not required
-Photons - needs further results (photon chemistry)
-Sensitivities - needs results
Discussion - needs above results
Conclusions - needs above results

Figures:
4.6 - Validation monoruns - runs ongoing
4.13 - Uranus North ion production - ongoing
4.14 - Uranus South ion production - ongoing
4.16 - Uranus heating - ongoing
4.19 - Peak rate altitudes, Uranus - needs runs
4.24 - H3+ densities for three cases Saturn - needs runs
4.25 - H3+ densities for three cases Uranus - needs runs
4.26-8 - Sensitivity graphs for Saturn, three whole 3D graphs - runs ongoing

Tables:
4.2 - Ion production Uranus - runs ongoing
4.4 - Heating Uranus - runs ongoing
4.5 - H3+ Saturn - needs runs
4.6 - H3+ Uranus - needs runs

Modelling required:
Validation runs (three cases - highly intensive due to powerful aurora) - ongoing
Uranus runs (two cases - very low intensity aurora) - ongoing
Chemistry module - coding to update for certain Steve based things, then runs using model atmospheres and ion production
Sensitivities - you can't miss these runs, they've been going for a year now... - ongoing

The problem with vanishing hydrogen in the chemistry routine has itself vanished as the coding mistake was discovered. The problem with H3+ being depleted compared to Grodent is likely to be due to the philosophy of the code (me not including transport terms) than anything else as the rates are very consistent and believable. Of course, the possibility that not having the H+ or He+ production rates reduces the amount of H3+ due to the lesser production through eqn 9 (lesser as some H+ appears chemically, so equation 9 does produce a little H3+) or through production of H2+ through charge exchange with He+ (also a production route for H+, which then adds to 9). Then there's the problem of high density regions requiring tiny timesteps to stop the densities overpowering fortran, and low density regions requiring low timesteps so their changes don't become so tiny they vanish in a rounding error... This at least is being worked on and the chemistry routine is starting to look a little like it could work in the future... though the runtime will be massive, especially when Steve's stuff goes in...

Final proof of the above arrived. The H3+ densities conform almost entirely to the H2+ ion production rate, which agrees with Chris' assessment that all H2+ goes to H3+ (within a certain tolerance). So using eqn 9 and charge exchange will top up the H3+. Plus another source of ionisation has been divined... photoionisation, which I forgot... I have the rates, or will have in a sec, but haven't stuck them in. Tut.

OK, have been fitting in the extra bit - variable resolution to cope with the different densities, and the test worked really well. Have had to adjust it as H3+ was being ignored (it needs a few iterations to get going) but got it done in the end. The only real question is how many iterations to allow it to have... as usual a case of results versus time - though the initial results were so good that may not be of concern. We shall see...

Further heating now cancelled due to lack of spectral generators to act as coolant in any atmosphere (asides from the H3+ coolant code from JIM etc). Having said that, lessons from the chemical rates module have informed corrections to the thermal profile one.

Also answered questions for BAS

BAS and four

Text:
Results
-Ion production and direct heating
-Chemistry (further)?
-Heating (further - Joule heating etc)?
-Photons
-Sensitivities
Discussion
Conclusions

Figures:
4.6 - Validation monoruns - needs runs
4.13 - Uranus North ion production - needs runs
4.14 - Uranus South ion production - needs runs
4.16 - Uranus heating - needs runs
4.19 - Peak rate altitudes, Uranus - needs runs
4.20 - Photoionisation Saturn - done!
4.21 - Photon heating Saturn - done!
4.22 - Photoionisation Uranus - done!
4.23 - Photon heating Uranus - done!
4.24 - H3+ densities for three cases Saturn(?) - needs coding, runs
4.25 - H3+ densities for three cases Uranus(?) - needs coding, runs
4.26-8 - Sensitivity graphs for Saturn, three whole 3D graphs - needs runs

Tables:
4.2 - Ion production Uranus - needs runs
4.4 - Heating Uranus - needs runs
4.5 - H3+ Saturn(?) - needs coding, runs
4.6 - H3+ Uranus(?) - needs coding, runs
4.7 - Solar ion production - done!
4.8 - Solar heating - done!

Modelling required:
Validation runs (three cases - highly intensive due to powerful aurora)
Uranus runs (two cases - very low intensity aurora) - ongoing
Chemistry module - coding to update for certain Steve based things, then runs using model atmospheres and ion production
Sensitivities - you can't miss these runs, they've been going for a year now... - ongoing

Data from photoionisation and heating now translated into appropriate graphs and tables. That bit of modelling is complete. I have also checked the photon model against some published calculations and it is fine.

Ok, so need numbers for Uranus as that is next. Numbers have been obtained. The model is prepped, keter is, well, keter. If successfull, these two will produce numbers for two tables and four graphs, as well as the seeds for the chemistry stuff, which will take care of two more graphs and the final two tables. Then there's just validations and sensitivities to do... Just. Other people don't really need keter do they?

Interupted by email from BAS, requiring some explanation of hi_tiros plus some hi_tiros_max datasets, all sent off.

Got the two Uranus models set up and running. Eventually... Of course, now I expect them to crash at the most inconvenient moment possible. All I have to do is wait to find out when that is...

Tiros

6.4 KeV
1M+ (Hurray!)

9.4 KeV
10,000ok

14 KeV
1000ok

20.8 KeV
1000ok

30.5 KeV
10,000ok

Have retried 46eV now that I've fixed the excitation recording thing and, unsurprisingly, I guess, the bus error has vanished. This may also explain why the current longer things haven't had any errors yet...

Also had a chat with Richard Horne, plus student, plus Alan, about TIROS and his attempt on it. In addition, have started the chapter on this stuff and it is going well and quickly.

Ok, have run 46eV for a million electrons. It looks like the bus error really is dead (for now). So, I should be able to do the rest of the runs fine (ie using Keter).

More work

Brief overview with the 'new era of Jovian auroral understanding' ie Steve's ideas on Makenzie's profiles. Yep, there are new ones, lots of them, with interesting things to look at.

One run finished (the last of the set that were running, meaning all I have to do is wait until the new regime is in place and set off the seven old ones again). Saturn5000 was the 12eV SD+1 run. It has been analysed.

Of course, first there is CTIP...

I have just had a look at putting the small increments thing in and it seems ok. Like everything else...

Sigh, "bus errror", should'a known it...

hmmm, will try a few runs on other computers using proton1...

Fails on rimmer

can't compile on C3

Going on keter... on the slow processors...

Trying out 31eV runs whilst waiting. It doesn't dip into the small increments level too deeply at this point, so may or may not avoid bus errors. On the other hand, ramping up the number of electrons fired does invite more errors to show their hand...

...bus error at 100k dammit!

Hmmm, difficult one. The lower energy stuff could probably quite happilly live without the small increments stuff, but the high energy stuff really needs it, otherwise there's the risk of crossing into an unrealistic pressure level. I'll run through the other energies and see if any of them can complete...

...one minor comfort, doing the 46eV lot, is that I do get ionisation in all pressure levels, as hoped.

...bus error at 100k

66eV
...100k again

96eV
...1M this time. Dammit... so close...

140eV
100k

206eV
100k

300eV
1M

440eV
1M

650eV
1M+ (hurray!)

950eV
1M

Don't yet have time to try out:
1380, 2030, 2980, 4400, 6400, 9400, 14000, 20800, 30500

I have actually remembered that since I have to divide all answers by a thousand to account for path length, 100k is more than enough anyway... and the answers (suggesting final peak rates from just shy of 1000 to just shy of 10,000 pcm3) is what is expected.

Must/may also do runs with pitch angle distributions, plus magnetic effects... after all...

Back to CTIP-type

Ok, still need to adjust the NDenses:
electron - common blocks, declarations, pdf, adjustments, selection - done!
strike - common blocks, declarations, pdf, adjustments, selection - done!
proton - common blocks, declarations, files, arrays, outputs - done!
proton1 - common blocks, declarations, files, arrays, outputs - done!
selectron - common blocks, declarations, pdf, adjustments, selection - done!
recoil - common blocks, declarations, pdf, adjustments, selection - done!
back - common blocks, declarations, pdf, adjustments, selection - done!
hit - common blocks, declarations, pdf, adjustments, selection - done!

But does it all compile? Yep.

Now I have a model with O, O2 and N2 being struck by incoming electrons, with no magnetic effects, as desired. However, this model contains old MSIS number densities. To convert to CTIP type completely, I need the CTIP densities in there as well as the altitude range.

The list of subroutines is:
randgen - no change
atom - no change
cross - no change
electron - changes
strike - changes
proton - changes
proton1 - changes
selectron - changes
recoil - changes
back - changes
hit - changes

Curent state of the input files:
NDens0 - Changes
NDens1 - Changes
NDens2 - Changes
NDens3 - Changes
Temp - Changes

...although I fear I may require one or two other pressure levels for expansion... we shall see...

ok, lets 'ave a look.

We're going from 1-600km to 80-580km, a change from 600 to 501 altitude levels.

Ok, changes in input files:
NDens0 - number of levels altered
NDens1 - CTIP numbers in
NDens2 - CTIP numbers in
NDens3 - CTIP numbers in
Temp - CTIP numbers in

Easy to follow...

So, subroutines:
electron - declarations, altitude incrementation, recording - done!
strike - declarations, alt. inc., recording - done!
proton - declarations, orientation adjustment, output - done!
proton1 - declarations, orientation adjustment, output - done!
selectron - declarations, alt. inc., recording - done!
recoil - declarations, alt. inc., recording - done!
back - declarations, alt. inc., recording - done!
hit - declarations, alt. inc., recording - done!

Compilation stuff - compiled first time

suspicious...

Quick test. 1keV gives 100+ km peak, sounds fine.

Another quick test. 10keV gives peak around 90km.

Yet another quick test. 30keV gives peak above 80km.

Seems ok so far.

100eV peaked - if that's the word - at about 130km. 50eV above it.

All the alts should be a little low as its a winter solstice atmosphere. They are indeed a little low, but not by too much in comparison to the atmospheric motion (we've lost about 20km cf the msis density height). Hmmm. Seems to work. For the really high energy stuff, I should add a lower atmospheric bin that can take the additional levels of precipitation and hold them for later uses (ie, total number of ionisations/excitations etc should remain equal as the atmosphere expands/contracts etc). Of course, further reasons for them being lower include the lack of mirroring or any pitch angle effects in there, plus no tilted field lines, as would be normal. Yep, a quick run raises the 1keV peak by nearly 10km when including the tilt. A pa spectru shouldn't be as significent a raise, but including mirroring and expansion, I think it's a pretty safe bet that the model's ok.

So, now I have a 'working' model, I can ruin it. I mean, use it. I need to feed through about a million electrons of each of the 19 DMSP levels. For the upper energies, this can be done immediately as they'll thermalise in the atmosphere above the lower boundary. For the high energy stuff, I'll need a lower atmosphere to help ascertain how much total ionisation there is - and the energy expended in creating it. Usefull here is the secondary/primary split, which tells me what the primary beam is doing and what the secondary beam then does. Changes in the primary beam affect the secondary beam - this is of paramount importance in the really high energy stuff. Not sure I'll actually use it here though...

We require:
31, 46, 66, 96, 140, 206, 300, 440, 650, 950, 1380, 2030, 2980, 4400, 6400, 9400, 14000, 20800, 30500eV runs.

Hmmm, should validate this thing soon... beyond the wishy washy validations and the validations of other near identical models. This one's new and has a defined purpose... plus it predates the arrival of the protonic version that should seal my fate...

It is total energy flux devoted to ionisation that needs to be conserved, so, in effect, it doesn't matter what the lower atmospheric composition is, just how many wallops I get from it... and from what in it... (in the case of those electrons of low enough energy to care).

Now, asides from anything else, I need to plot out what should happen for the proton version. I require:
O, O+, O-, O2, O2+, O2-, N2, N2+, N2-, H, H+, H-, e-
...and a grid of cross-sections between each of them and themselves, each one equivalent to the size of the e- grid.

Frightening innit. And that's just a 'surface' (as in scratching the) model... A proper one would involve everything down to bare nuclei, plus N stuff etc. But could be a way to start off DICE as a proper thing...

Ok, a real 'surface' model would just take the primary beam ionisations, but that wouldn't be any fun, would it?

Now a more interesting example would be could I construct a series of models similar to the electron one, but for each of the proton constituents (H, O, O2, N2), then find a way to coadd the resultant primary beams one by one?

That's it for today

Also sketched out an outline for the chapter relevant to this stuff

Next thing

Ok, the CTIPtype RIDE has lost its magnetic field. Next thing's to lose all the extraneous atmospheric species:

Current state of the modules:
randgen - No need to change
atom - Needs to be adjusted
cross - Needs adjusting
electron - Needs adjusting
strike - Needs adjusting
proton - Needs adjusting
proton1 - Needs adjusting
selectron - Needs adjusting
recoil - Needs adjusting
back - Needs adjusting
hit - Needs adjusting

Curent state of the input files:
NDens0 - Remains
NDens1 - Remains
NDens2 - Remains
NDens3 - Goes
NDens4 - Becomes NDens3
NDens5 - Goes
NDens6 - Goes
NDens7 - Goes
Temp - Remains

Note this is an intermediate step, which is why I don't just keep NDens1-3. I'm recreating RIDE from its own number densities before putting in the new ones.

Extraneous NDens' removed, N2 NDens renamed

Adjustments:
atom - adjusted arrays - done!
cross - adjusted echeck, adjusted ecross, adjusted cross - done!

Ok, for when I return:
electron
strike
proton
proton1
selectron
recoil
back
hit

Conversion to CTIP type...

I have copied over the various bits of RIDE Earth. The makefile lists the following modules:
randgen - Random number generator
atom - atomic and molecular information file
cross - cross-sections database
electron - initial transport (primary beam)
strike - forward transport (primaries)
proton - manual input version of main program file
proton1 - auto version of main program file (uses input files instead of typing)
selectron - secondaries initial transport file
recoil - backward transport (primaries)
back - backward transport (secondaries)
hit - forward transport (secondaries)

These need to be converted to remove magnetic effects as well as H, He, Ar and N. The altitude range needs to change from 0-600km to 80-580km.

Input files:
MB - Magnetic strength file
MDec - Declination angle
MDip - Dip angle
NDens0 - zeroed electron density file
NDens1 - O densities
NDens2 - O2 densities
NDens3 - N densities
NDens4 - N2 densities
NDens5 - H densities
NDens6 - He densities
NDens7 - Ar densities
Temp - neutral temperatures

Need to get rid of the three field files as well as NDens3, 5, 6 and 7 and replace the remaining ones with those appropriate to the new thing.

Three magnetic input files have been deleted.

Now to rid the various other files of their footprints:
randgen - No footprint
atom - No footprint
cross - No footprint
electron - Removed common block, removed declarations, removed calculations - done!
strike - Removed common block, removed declarations, removed calculations - done!
proton - Removed common block, removed declarations, removed calculations, removed input files - done!
proton1 - Removed common block, removed declarations, removed calculations, removed input files - done!
selectron - Removed common block, removed declarations, removed calculations - done!
recoil - Removed common block, removed declarations, removed calculations - done!
back - Removed common block, removed declarations, removed calculations - done!
hit - Removed common block, removed declarations, removed calculations - done!

Done. And successfuly compiled too.

Work!

Makenzie has produced a corrected profile to be modelled. That with Alex's stuff should keep me going (plus validation graphs).

But first - marking. Now done (Howarth that is... have asked Raman and should get his stuff tomorrow/monday)

Supercomputer queues are to be altered again, making it possible to rerun the six 'dead' runs.

Have spoken with Alex about the proton oval

Also have interpolated out the CTIP atmosphere for the runs. I have the energies from the DMSP thing, bit worried about not having H, He at least (also N and Ar), which could reduce the overall ionisation rate (not so much Ar, but at the top, definately H and He). We shall see... shouldn't be too bad as O remains about ten times the next thing, and has a larger cross-section...

...even so...

Oh yes, and attended Steve's H3+ talk. As well as a later one involving Makenzie's profile...

So, now marking's over what's left to do?

Alex stuff - 19 runs of a million electrons into a modified version of RIDE Earth according to DMSP energies
Makenzie stuff - fit profile (there, sounds easy)
Grodent stuff - validation
Thesis stuff - write up whichever of the above gets done first...

Marking - whenever

we'll see...

Have checked the Ovation model Alex/George are using to define the auroral oval - it includes ions!

More TIROS and marking

Have answered some simple questions on TIROS

Plus recovered posters from old office

Marking Howarth

Moving, just keep moving...

The major part of the day was spent shifting from one office to another

Also had chat with Alan about final six months, though he seemed unprepared, which makes me wonder why he insisted on a chat (or at least did on Monday).

Got files off Alex giving temps, densities etc for pressure levels in the CTIP run. Need to find out the top altitude just to get a final feel for what is going on. Once that is done, run can be dun. Then on to the more complex bits... for Alex. Adjusting for dip angles, changing constituents, changing pressure level heights etc etc etc. In the dim and distant future, pitch angle spectra for the energy channels could also be dreamt up and a few runs could be used to angle those properly...

Then there's protons...

It'll make a good chapter and a good template for work to do with BAS and Steve.

Marking. Howarth.

Atmospheres

Have arranged (after some negotiation) O, O2 and N2 from CTIP, but will have to wait until they arrive...

Just had a visit from the shadowy heads of computing complaining that I actually use the machines... They made a miscalculation. They looked at the run that finished yesterday, noticed it ended close to midnight on the 13th of March, noted that it was set off on the 12th of feb, then forgot that february has 28 days, they seemed to have counted it as 31, meaning the run lasted 32 days. Three doctorates and a professorship between them...

All of anasuya's additional marking done. I assume... All those marked IOT (in on time?) and one handed in not on the sheet. Though there is a name on the sheet, not marked as being IOT, which was missing from the folder. Curious.

More and more and more...

Computer problems to start the day off. Following the collapse of APL email, starlink email and UCL email, the APL server got fried.

Finished off Raman marking. Got given some mysterious scripts of Howarth that had evaded the last tranche of marking... odd. They were dealt with and returned to sender.

Also worked with Alex to create a second TIROS replacement, not linked to the BAS one. Could this mean I publish two new auroral oval models for the same atmospheric model in direct competition with each other? Not really, the BAS one is a substorm extension, the Alex one is a quiet time model, in effect we'll switch between them depending on what we're doing as the BAS one will be more computer intensive.

...and of course keep TIROS just incase something goes wrong...

But at least with Alex first stage is done, formatting the spectrum, chopping it up and deciding what will happen to it. The next stage is generating profiles, the third stage will then be doing all my little additions (literally back of the envelope, the envelope is next to the comp - I need a touch pad to doodle onto the Mac with) to conserve energy (yes that minor second law of thermodynamics thing). As Eddington said (ish), if your theory goes against Maxwell's equations, so much the worse for Maxwell, but if your theory contravenes the second law of thermodynamics, there's nothing to do but throw up your hands in defeat...

Must press the case for protons in both models...

Hmmm, looks like a million or so electrons will do for each of these levels. No adjustments required for RIDE to operate as it all ends at 30keV, well below RIDE's current nominal upper limit.

Same stuff

Yep, marking. Halfway through the physicists.

Also discussed some stuff with Alan about a new version of TIROS. Looks like electrons fluxes etc can be generated through a set of calcs. I then have to come up with some sort of CSDA model seeded by my own that does the rest. Very possible. Have worked out enough for it to be better than TIROS, just a case of how much better.

Marking

...and TIROS

Marking

Marking

Plus updated TIROS entry and had quick meeting with Steve about Makenzie's stuff.