Hmm, I don’t know what you mean about the NS info being bunched. I’ve not seen that before. But if data is not being displayed, it is typically due to the ENABLE variable settings in the Config Settings at your Heroku or Azure admin page. My ENABLE is set to:
delta direction upbat timeago devicestatus upbat maker profile careportal boluscalc food rawbg iob cob bwp cage sage iage basal bgipump bridge loop bridge override
There are also several new variables that should be defined in Config Settings specifically for Loop if you are using the JoJo branch. I prefer the JoJo branch over the omnidev testing branch as JoJo provides the Overrides allowing users to create their own temp basal overrides. This is really useful for exercise or anytime you would normally use a temp.
I use Tidepool, too, and love it! Yes, it must be refreshed but not a big issue for me, as I only occasionally view it.
Is he doing pre-bolus? You still need to pre-bolus, just like you would pre-loop. None of that changes with Loop. If he is going high maybe you need to ensure he is pre-bolusing a sufficient amount of time to see the BG trend arrow angle down?
So you are probably using the Rapid-Acting Child DIA. That should be fine and will give you 6 hours of DIA if you have not changed the code in xCode.
You also may want to review your Correction Range. Loop could be giving a zero basal if the Correction Range is too high. Just another thing to look at!!
That is great you are teacher!! Lucky you to have the summer off!! Post again if you have any questions or you need help w/ the NS site. I’m not an expert but will try to help where I can.