Dd Form 1170: Fill & Download for Free

The Royal Challengers Bangalore decided to keep hold of their and India captain Virat Kohli and at what cost? Well! Rs 17 crore.This amount made Kohli the highest paid player in the history of the tournament toppling what Delhi Daredevils paid for Yuvraj Singh in 2015. Kohli was the first retention for RCB this year and according to the IPL salary caps -- it was supposed to be Rs 15 crore -- however, the RCB has paid two more and made him the most valued player in the history of the 11-year-old tournament.Mahendra Singh Dhoni was also retained by the returning Chennai Super Kings and so was Rohit Sharma by the Mumbai Indians in the top salary cap category of 15 crore each -- making them the joint second highest paid players in the league.Here is a list of the highest-paid cricketers in the IPL.VIRAT KOHLIRetaining Kohli was a no-brainer for the Royal Challengers and it turned out to be a costly move. But what comes with it is more or less assured peformances.Kohli was in tremendous form in 2017, hitting 2818 runs across all the formats for India before flying off to Italy with Anushka Sharma to tie the knot.Kohli has played for RCB since the inception of the league and has hammered 4418 runs from 149 matches at an average of 37.44. He also became the fastest player to reach 4000 runs in IPL history and his best season was 2016 when he smashed 973 runs including four hundreds at an average of 81.08.Along with Kohli, RCB retained AB de Villiers and young Sarfarz Khan for 11 crore and 1.74 crore respectively. The duo are set to form the backbone of the team going into the 2018 season.YUVRAJ SINGHDelhi Daredevils paid a whopping Rs 16 crore for the swashbuckling all-rounder back in 2015 -- making him the record buy in the history of the IPL then. Incidentally, he was also the record the year before, when RCB paid a 14 crore to get his services but released him the following year because of his bad form and fitness.Yuvi scored just 376 runs from 14 games and took five wickets for Kohli's team and the following year he just hit 248 runs and took one wicket for the DD and was released again. Since then, he has played for the Sunrisers Hyderabad and has scored 236 and 252 runs respectively in 2016 and 2017.Yuvraj was released by the Sunrisers for this year's auction and he is currently out of the Indian set-up and is struggling to pass the Yo-Yo Test but his past exploits, experience and flamboyance is a bonus for any team and he is expected to fetch decent amount in the auction.MS DHONIMS Dhoni's return to CSK was written in the stars and that did happen on Thursday when the IPL 2018 player retention took place.CSK kept him for a whopping Rs 15 crore -- the base salary for the first retained player. Along with him CSK retained Suresh Raina and Ravindra Jadeja.But Mahi's return has got the fans excited the most and him as well. Dhoni has led CSK to two trophies and four finals in eight years of the tournament.Dhoni, who played for the Rising Pune Supergiant in the last two seasons has scored 3561 runs from 159 matches in the IPL. He has hit 17 fifties.For CSK, Dhoni has smashed 2987 runs from 129 matches in the first eight seasons.His form in the shorter formats was questioned toward the end of 2017 but he rescued his team and played some crucial knocks for India in the recently concluded three-match T20I series against Sri Lanka to squash all of them.He is now expected to lead the line as usual and take CSK back to where they belong according to the Whistle Podu loyalists.ROHIT SHARMAMumbai Indians retained Rohit for the same amount as CSK did with MS Dhoni - Rs 15 crore.Retaining Rohit was a no-brainer for Mumbai just like Kohli was for RCB. He has led them to thre IPL titles in 2013, 2015 and 2017 -- the most by any team in the tournament.The Mumbaikar has been playing for them since 2011 and took over the captaincy in 2013 and has never looked back since.He has a total of 4207 runs from 159 IPL matches and one hudnred. Out of which, out of which 1170 runs have come during his time with the Deccan Chargers from 2008 to 2010. He played 45 matches for them.Rohit was retained alongside Hardik Pandya and Jasprit Bumrah and the trio will form the core of the squad. He recently captained India to ODI and series victories against Sri Lanka and is fully expected to help Mumbai defend their title in 2018.BEN STOKESHe was the star-attraction in 2017's IPL auction and it was evident right from the beginning. He was priced at Rs 2 crore and was expected to go big and he did. So much so, that Mumbai Indians were holding the baton even before the auctioneer Richard Madley could name his base price. All eight franchises were after him and there was an aggressive battle between Mumbai Indians (MI), Royal Challengers Bangalore (RCB) and Delhi Daredevils (DD).Later Sunrisers Hyderabad joined in but he was at last bagged by the RPS for a whopping fee of Rs 14.50 crore. He has now become the second costliest player in the history of the IPL auctions behind Yuvraj Singh, for whom the DD paid 16 crore in 2015.Stokes has been in brilliant form since last year and was one of the star players for the England team in their recent series in India.And he didn't disappoint his buyers. The mercurial all-rounder hit 316 runs and 12 wickets from 12 games for the RPS. He guided them to the qualifiers before joining national duty.He is again expected to go big as all-rounders of such calibre are going to come far and wide and teams will jump on the opportunity of having him on their side.

Palindrome days are those days whose date is similar to read either from first to last or last to first.FOR EXAMPLE:-most recent palindrome day is 02/02/2020palindrome days that can be possible if you consider in DD/MM/YY format should follow these rules:If last two digits of year is less than 10, it should be 01 , 02 or 03.(as it’s reverse turns into day which is less than 10)if not the 1st case then units place should be 1 , 2 or 3 & if units place is 3 then tens place is either 1 or 0.coming to month , only 01 & 11 (ie, Jan & Nov ) can only satisfy to be palindromeNow this might not be answering your question. because Palindrome is not a Nature’s phenomenon. It is some sort of playful observation that we humans created/noticed.so definitely they cant be coming in specific order/Frequency.But identical palindromes come once in hundred years.(considering DD/MM/YY format)EDIT1:-IF YOU CONSIDER DD/MM/YYYY FORMAT ALSO YOU CAN MAKE SUCH RULES.I MADE A C++ PROGRAM TO FIND PALINDROME YEARS FROM 1–2100.WHICH ARE AS FOLLOWS:10/10/010120/10/010230/10/010301/10/011011/10/011121/10/011231/10/011302/10/012012/10/012122/10/012203/10/013013/10/013123/10/013204/10/014014/10/014124/10/014205/10/015015/10/015125/10/015206/10/016016/10/016126/10/016207/10/017017/10/017127/10/017208/10/018018/10/018128/10/018209/10/019019/10/019129/10/019210/01/100120/01/100230/01/100301/01/101011/01/101121/01/101231/01/101302/01/102012/01/102122/01/102203/01/103013/01/103123/01/103204/01/104014/01/104124/01/104205/01/105015/01/105125/01/105206/01/106016/01/106126/01/106207/01/107017/01/107127/01/107208/01/108018/01/108128/01/108209/01/109019/01/109129/01/109210/11/110120/11/110230/11/110301/11/111011/11/111121/11/111231/11/111302/11/112012/11/112122/11/112203/11/113013/11/113123/11/113204/11/114014/11/114124/11/114205/11/115015/11/115125/11/115206/11/116016/11/116126/11/116207/11/117017/11/117127/11/117208/11/118018/11/118128/11/118209/11/119019/11/119129/11/119210/02/200120/02/200230/02/200301/02/201011/02/201121/02/201231/02/201302/02/202012/02/202122/02/202203/02/203013/02/203123/02/203204/02/204014/02/204124/02/204205/02/205015/02/205125/02/205206/02/206016/02/206126/02/206207/02/207017/02/207127/02/207208/02/208018/02/208128/02/208209/02/209019/02/209129/02/2092Just for reference :}

The bottom line of this answer is that unless I’ve made a mistake in the calculations below, Google is an unreliable source of planetary locations.I should explain why I asked this question. I wanted two data points of each of Jupiter’s and Saturn’s positions, spaced far enough apart in time to allow me to draw their respective trajectories on the celestial sphere in order to see for myself when they were nearest each other.One would think that simply asking Google “where is Jupiter” would suffice for this purpose. On December 21 at around 3:15 pm Pacific Standard Time (2315 UT1) Google reported the following.Jupiter RA 20h 10m 33s Dec -20° 32′ 38″Saturn RA 20h 09m 03s Dec -20° 30′ 19″Twenty minutes later the 33s in Jupiter’s RA had advanced to 34s but Saturn’s 03s hadn’t changed. A further twenty minutes later Jupiter’s 34s hadn’t changed but Saturn’s had advanced to 04s.If RA had been given to two more decimal places, those 20 minutes would have been long enough to plot Jupiter’s and Saturn’s trajectories and infer where they were closest. But with only 15 arcseconds of RA accuracy, obviously I was in for a much longer wait than I’d been expecting for such a simple task, whence my question.In retrospect I should have specified in my question that the source of higher accuracy shouldn’t be too much harder than asking Google “where is Jupiter?” Buying commercial software seemed to defeat the purpose when simply waiting a lot longer would solve the problem, while I could spend the intervening time on other projectsWhich is what I did. Three days later, on December 24 at 11:40 am (1940 UT1), Google returned the following.Jupiter RA 20h 13m 12s Dec -20° 24′ 34″Saturn RA 20h 10m 21s Dec -20° 26′ 29″Jupiter’s position moved 159s of RA = 2385″ and 484″ northwards), while Saturn moved 78s of RA = 1170″ and 230″ northwards. No problem with precision now.For accurate projection of the celestial sphere onto a sheet of paper, the RA needs to be scaled down by the cosine of the declination, for the same reason one has to do that to longitude on Earth, otherwise square plots of sky will show up as rectangles instead of squares. cos(20.5°) = 0.937, so Jupiter’s RA movement is really 2234″ while Saturn’s is 1170*0.937 = 1096″.The bit of the celestial sphere we’re interested in starts at RA 20h and declination 20° South. On Thursday Jupiter had ended up (13*60 + 12)*15*0.937 = 11132″ east of 20h and 24*60+34 = 1474″ south of 20° S, while Saturn’s corresponding coordinates are 8728″, 1589″. So Saturn is south of Jupiter today.To back up to Monday’s position. for Jupiter we need to subtract (2234″, -484″) and for Saturn (1096″, -230″). (All those numbers are from the two paragraphs preceding the preceding paragraph.) As it turned out however I needed to back up even further, namely by two more such subtractions going more than a week back. The final trajectories then each had four points, arranged chronologically as follows.—JUPITER—SATURN—dd hh:mm4430 2926 5440 2279 16 06:256664 2442 6536 2049 19 02:508898 1958 7632 1819 21 23:1511132 1474 8728 1589 24 19:40The first two columns are Jupiter’s RA and declination, and the next two are those for Saturn, all in arcseconds (with RA scaled to make the plot conformal, i.e. preserving right angles). The fifth column is the date in December (16th through 24th) and the rest is time in hh:mm on that day, UT1 (8 hours ahead of California time).These four dates yield the four lines in the following plot from left to right, each showing the angular distance between the two planets. Saturn is on top, moving more slowly than Jupiter below.It’s very obvious that they were closest together on December 19 at around 02:50 UT1.But that’s a full three days earlier than what the newspapers were saying!So who’s wrong?This was sufficient motivation to try Stellarium from Github, which gives RA to ten milliseconds (0.15 arcseconds). It has an ephemerides feature that lets you compare any two bodies for things like angular distance. According to Stellarium the angular distance between Jupiter and Saturn was almost exactly 0.1° at 17:40 UT1 on December 21.That’s in good agreement with what the newspapers were claiming.Maybe I’ve made a mistake somewhere, but I’ve shown all my work so if I did then it should be possible to find my mistake. Here again are the two datapoints supplied by Google that my diagram above is based on.December 21 23:15 UT1Jupiter RA 20h 10m 33s Dec -20° 32′ 38″Saturn RA 20h 09m 03s Dec -20° 30′ 19″December 24 19:40 UT1Jupiter RA 20h 13m 12s Dec -20° 24′ 34″Saturn RA 20h 10m 21s Dec -20° 26′ 29″But if I haven’t made a mistake, then Google would appear to be an unreliable source of planetary positions.