A Weekly Dose of President Trump - Trump Family Train 7/17/19 to 7/31/19

Friends and Deplorable's | July 17, 2019 | DollyCali

[DollyCali]

THE WEEK THAT WAS
THE GOOD, THE BAD
THE UGLY

GOOD ~ G-20 Summit in Japan

VERY GOOD ~Trump does Independence Day!

BAD ~ The gang of four ugly women in Congress

UGLY ~AOC “crying” at the border and Nike (tied)








President Trump does G20
Then Visits S Korea & Military
Then visits N Korea!!!!!
GRAPHIC COVERAGE IN POST ONE




Welcome all you Deplorables to this week's edition of the Dose!
This is EVERYTHING TRUMP.
Administration, family, frustrations, joys, winning!
We welcome your research, your commentary,
your personal OT sharing and your presence.
Even if you do not share a lot, just check in and say hi.
Lurkers are welcome to become posters!




Deplorably wonderful these past weeks

President @realDonaldTrump signed a bill that delivers $4.6 billion for humanitarian assistance and security to our southern border.(7/1/19)



  President DJT shows the world
how to have a birthday celebration! (7/4/19)

Returning to DC(7/14/19)






Inviting the conservatives.... (insert smiley face)(7/11/19)

Volvo Trucks announced today they are expanding their plant with $440 million in investment and bringing 770+ new jobs to the NRV.  A number of workers were wearing Pro-Trump shirts and hats.(6/28/19)





Ah the Memes of fun and truth:(6/24/19)

























Keep the Truth coming Mr. President
Keep on Tweeting!

[hoosiermama]

Let him know we are praying for him and support him

https://www.whitehouse.gov/contact/

[djstex]

I love this story Raisin Cain!

[freepersup]

BOOM!

[weston]

America will never ever be a socialist country!!

AMEN!

[pax_et_bonum]

Yep, none of us are perfect.

[pax_et_bonum]

Lol!

Couldn’t resist!

[pax_et_bonum]

Me, too!

[pax_et_bonum]

“This big, beautiful, mighty ship, we have turned it around.”

[djstex]

His stories are the best!

[pax_et_bonum]

Thanks for the link!

[weston]

We spent trillions of dollars fighting in Iraq and we still have to turn the airplane lights off to land safely there.

So true... outrageous. He says it’s because we didn’t fight to win. “I fight to win!”

[pax_et_bonum]

Yes, they are!

[djstex]

What a Beautiful Baby!
Love Our President talking and seeing all of us!

[Lakeside Granny]

Trump recognizes a beautiful baby that his daddy is holding up.

[hoosiermama]

Check into Jim’s thread and show your support to OUR president

https://www.freerepublic.com/focus/news/3764462/posts?page=1

[freepersup]

We Deplorables are praying for your protection and wisdom. Period. Full stop. Thank you sir for laying it all on the line. We have your back at every turn . Your rallies are the proof. More people are outside, than inside. Full speed ahead! I’ve followed about 75% of your rallies, attending one in AZ., at Fountain Hills. Stay the course. God Bless You, and Your Administration!

[exit82]

Did I see a big “Q” drawn on the back of that baby’s shirt?

[freepersup]

We ARE a movement!

[STARLIT]

https://destevez.net/2019/07/galileo-constellation-outage/?utm_source=dlvr.it&utm_medium=twitter

The signal health status field has two bits, so it supports four different values: 0 for “signal OK”, 1 for “signal out of service”, 2 for “signal will be out of service”, and 3 for “signal component currently in test”. Keep in mind that these values refer not only to the signal being currently tracked, since an INAV page has fields for both E1B and E5b and the almanac entries also include the health status of each of the satellites in the constellation. Therefore, it is perfectly normal to see a “signal out of service” somewhere, probably referring to a signal other than the one currently being tracked (which is most likely not out of service).

The problem is that misidentifying the day associated to an ephemeris batch will cause huge orbit errors, because the time to propagate the ephemeris is computed incorrectly. Therefore, since 2019-07-15 09:50 we are seeing reports of receivers giving absurd positions for Galileo satellites, such as negative elevations.

The behaviour of the data validity status is more interesting. Satellites E01, E03, E04, E09, E24, E25 and E36 show a value of 0 (OK) for both E1B and E5b, while satellites E05, E11, E19, E21, E31 and E33 show a value of 1 (not OK) for both E1B and E5B. Of course, the correct data validity status in this outage situation is 1.

The reason why only half of the satellites are showing a data validity status of 1 is unknown. I have heard rumour that depending on the on-board software, some satellites are able to detect that the ephemeris are too old and set the data validity to 1 automatically, while others need to be commanded by a groundstation. This still leaves open the question of why haven’t all the satellites being commanded to transmit a data validity status of 1.

The report by the NAVSAS group includes similar results, showing a more extensive list of what satellites have the data validity status bit set to 1.

Finally, it is interesting to take a look at the almanacs in the gal_almanac.xml file. This file contains almanac entries for E01, E02, E03, E04, E05, E07, E08, E09, E11, E12, E13, E15, E19, E21, E24, E25, E26, E27, E30, E31, E33 and E36, which were all the active satellites before the outage. The TOW and WN for each of the almanac entries in this file corresponds to 2019-07-11 00:50. The health status for all the satellites is 0 (OK), except for E02 and E26, which have a status of 2 (will be out of service) for the E1B signal........part of article

[djstex]

So Trump!
He’s all about US!