r-spacex / spacexstats-react Goto Github PK

View Code? Open in Web Editor NEW

209.0 15.0 57.0 38.72 MB

SpaceXStats, with React and using the SpaceX API

Home Page: https://www.spacexstats.xyz

JavaScript 5.02% TypeScript 94.98%

react space spacex statistics

spacexstats-react's People

Contributors

Stargazers

Watchers

spacexstats-react's Issues

Rename "used" to "Flight-Proven" ?

What do you guys think about it?

Falcon 9 Launch Count subtext

Below the Falcon 9 Launch Count, it is stated that Falcon 9 "is not far from its last iteration (Falcon 9 v1.2 Block 5) enabling rapid reusability." They have now reached Block 5, so the not far from wording could be removed. My suggestion:

It is currently flying in its final iteration (Falcon 9 v1.2 Block 5) enabling rapid reusability.

Up mass by year

u/Bailliesa in SpaceX thread comment requested feature:

total up mass by year (similar to launches)

Add scrolling/zooming to charts

Wrong launch date for SXM-7

The date for SXM-7 is malformed or otherwise invalid. This leads to a wrong next launch time as well:

Might be an issue with the SpaceX-API data.

Payload mass in every launch

u/Bailliesa in SpaceX thread comment requested feature:

Add payload mass as a subscript to the launch count ie Falcon 9 - 49 launches (xxx total payload mass)

Heaviest payloads with booster landing

u/Bailliesa in SpaceX thread comment requested feature:

heaviest LEO/GTO with booster landing (ASDS/JRTI/RTLS)

Better planned launches on Launch History

The proposal is to merge 2017 and "planned 2017" into single stacked bar with 4 yet planned launches in the year.

Hours worked

In the last panel (same as #23), the number of hours worked is countless. Beyond the joke, it would be interesting to put an estimation of man-hours put into the project.

Change background images for LC-39A and VAFB

Launch count comment "as of Invalid date"

${format(turnarounds.lastLaunchDate, 'MMMM YYYY')} in main.js line 52 returns an invalid date error that is then shown in the text. As of today the launch data for the last launch is for Iridium NEXT 8 (Launch 74) which includes a launch date in its JSON from the SpaceX-API. Therefore probably some date manipulation is done incorrectly.

Add keyboard shortcuts

Up/down to mobe between sections
Left/right between tabs

timelines falcon heavy

The last panel showing Elon Musk's bet, Time since founding and Falcon Heavy is a bit off for the Falcon Heavy slide, showing a launch in 5 days.

Or maybe it's the deadline given by an official ? The website is then unclear.

Dragon - CRS Flights - CRS - CRS 23 - Wrong flight time

CRS 23 indicates 2810 hours of flight time, but the flight time is similar to previous missions, about one month, or 700-800 hours.
https://www.spacexstats.xyz/#dragon-crs
From wikipedia:
Launch date 29 August 2021, 07:14:49 UTC
Landing date 1 October 2021, 02:57 UTC

Dragonriders = 2

Two astronauts are now flying on a Dragon :-)

Mass to Orbit stats?

I'm curious if there is any way to calculate up mass to orbit per launch.
I would be very entertained watching mass to orbit count up during the year, and especially per booster.
F9 is quite a bit smaller than Saturn V sure...but at some point the actual delivered mass to orbit by a single booster will get there. ... won't get it to the moon...but it will still be an interesting milestone.

Launch history success rate launch #101 is in the wrong place in the chart

The launch number 101 is between launch 96 and 97.

Might be an issue with some underlying data but as far as i can see a sorting in successRate.ts should fix this.

Handle Falcon Heavy side-boosters in stats before Falcon Heavy launches

That should be ok, I have six months to do it

Booster Reuse graph on hover has no linebreaks

When hovering over the b1060, b1058 and b1051 sections in the reuse bar chart, their tool tips showing which missions they have launched are cut off as they are single lines which are longer than the divs they are contained in.

Add some line breaks, or make the list of missions bullet pointed?

Wrong missions displayed for turnarounds

From /u/retiringonmars:

I spotted few errors with respect to pad turnaround in SpaceXStats:

The fastest turnaround at LC-39A isn't between Inmarsat-5 F4 and Intelsat 35e, as BulgariaSat 1 flew between these two launches. It should state "between Intelsat 35e and BulgariaSat 1".
The fastest turnaround at SCL-40 isn't between TurkmenAlem and CRS-4, as these were seven months apart. It should state "between TurkmenAlem and CRS-6".

Other wise, great work, guys!

No doctype

Hey, I noticed that the HTML returned by http://www.spacexstats.xyz/ doesn't start with a doctype (<!DOCTYPE html>).

I'm not familiar with React, so please close if I'm just missing something and it's intentional. But I thought it's generally a good idea to declare a doctype, or browsers will render it in quirks mode.

Incorrect number of planned launches for 2018

The launch history graph still shows 10 planned launches as part of the initial goal of 30 for 2018, which obviously is not going to happen at this point. Planned launches should either be removed or be based on the launches/upcoming API endpoint to prevent this from being an issue in the future.

Don't display launch mass when null

Follow-up to r-spacex/SpaceX-API/issues/52

In launch history compare with other launch providers

Using https://launchlibrary.net

Consider deploying this app to Vercel

I just discovered, cloned, installed, compiled and opened this app, and it's rather nice.

I'd suggest hosting on Vercel (they have a free tier available): https://vercel.com/
Their service has automated CI/CD stuff, so you don't have to do much for that.

Consider checking it out

Create an account
Link the repository
Add the link (https://something.vercel.app) to the README.md
Add the link to the GitHub repo description

Improvements to launch history

Hide "0" lines in the tooltip
Add vertical axis on the right
Add planned launches (how?)

Fonts not consistently rendering

Per #14. Possibly not downloading the font?

Edit: As a wildcard is used here, it is possible the fonts are defined after it's supposed to be used. This would explain why it depends on the system, as the exact behavior would likely depend on the CSS parser (it's single-pass).

Launch Count Total text blurb is incorrect

As of October 2017, SpaceX has launched 54 rockets, carrying a variety of payloads to multiple destinations;including LEO, GTO, L1, and the ISS. SpaceX currently has a manifest of over 70 flights that will fly over the coming years.

Pretty sure that should be As of $MONTH_OF_LAST_LAUNCH_UPDATE. Perhaps you could calculate the month of turnaroundsData.lastLaunchDate and just put that in place of the hardcoded month?

More data about fairings?

Great page. I come there to find some data about re-using of the fairings. I'd love to see more detailed data about the fairings, e.g. which fairings re-flew how often, was it scooped from the water of caught by the net?

Feel free to close this issue if you feel it's inappropriate.

Launch Count Total subtitle

Currently it says:

As of October 2017, ...

The date is hard coded into the text. Should either be a date variable showing the current date or like in the F9 Tab

To date,

I would have created a pull request, but i am not familiar with the setup, sorry.

www required

the site is no longer reachable under spacexstats.xyz www.spacexstats.xyz does still work. is this intentional?

Add list of missions on hover of customers pie chart

Minor Issue. No detection that launch time is in the past.

For example, today, where Zuma is was due to launch NOV 18TH, 1:00:00AM (UTC+00:00). Loading the website will say 1DAYS 13HOURS 41MINUTES 21SECONDS and then the clock will count down. When actually we are getting further away from the launch date, refreshing the page then demonstrates this.

Would it be possible to have a launch date calculation and counter that appreciated negative numbers and so could display the timer as overdue?

Edit:
I link this might be the responsible line

spacexstats-react/app/components/stats/TimeStat.js

Lines 46 to 47 in dda9336

 if (this.duration < 0) { 

 this.duration = - this.duration;

With the countdown timer written here:

spacexstats-react/app/components/stats/TimeStat.js

Lines 54 to 73 in dda9336

 updateTimer = () => { 

 const factor = this.props.type === 'countdown' ? -1 : 1; 

 this.duration = this.duration + factor; 

 let secondsLeft = this.duration; 

 const days = Math.floor(secondsLeft / (60 * 60 * 24)); 

 secondsLeft -= 60 * 60 * 24 * days; 

 const hours = Math.floor(secondsLeft / (60 * 60)); 

 secondsLeft -= 60 * 60 * hours; 

 const minutes = Math.floor(secondsLeft / 60); 

 secondsLeft -= 60 * minutes; 

 const seconds = Math.floor(secondsLeft); 

 this.setState({ 

 days: days, 

 hours: hours, 

 minutes: minutes, 

 seconds: seconds, 

 }); 

 }

Unfortunately, I don't have enough experience with react to fork, tweak this and test it myself. Although with the instructions on the README.md I may have a go when I get a moment!

Merge Launch and Landing histories

Planned/Failed launches and launches with no recovery attempts would have same visualization as it is now on Launch History graph.

But all of the launches with attempts of first stage recovery can have its bar split in two halves. Left would represent the launcher (New/Used) and right would show landing/recovery status (similar to current Landing history graph).

Launch count

I have brought this up before but your launch count is still incorrect. On the site it states that there have been 44 Falcon 9 flights, clearly including Amos-6. But there only have been 43 launches so far. Amos-6 didn't launch. If you want to include Amos-6, please rename the section to 'Mission count' but I would prefer you just change the counter.

Incorrect number of Starlink satellites

The payloads section Starlink tab currently still shows 2 satellites when it should now be 62. This appears to be coming from a hard-coded "internetConstellation" variable in /app/helpers/payloads.js. I don't see any way this data could be pulled from the API currently as the number 60 is not anywhere in the data about the Starlink launch. Perhaps a temporary solution could be to count the number of launches containing "Starlink" in the mission_name, multiply by 60, and subtract 58 (for the Paz/Tin-Tin mission). This of course is not ideal as it assumes every launch from here on out will have 60 satellites, but it would be more correct than the current hard-coding.

api.spacexdata.com doesn't seem to supply future launch data for 2023

Possibly this is out of jurisdiction for this site, but there are many launches observable for 2023 on https://www.spacelaunchschedule.com/ or https://spacelaunchnow.me/launch/upcoming/ or other sites. I don't know who owns api.spacexdata.com and why it's not updating. I polled the https://api.spacexdata.com/v5/launches endpoint with a REST client and really the last item was from December.

Flight stats incorrect for reused dragon capsules in commercial crew section

https://github.com/r-spacex/spacexstats-react/blob/master/src/components/blocks/Dragon/charts/commercialCrewFlights.ts#L34 incorrectly assumes that flight time of the payload.dragon is invalid when payload.reused is set, and thus defaults to 0.
I think that that is incorrect.

Currently, this means that flights with reused capsules are displayed as if they had 0 flight time, which is obviously incorrect.

Site is broken with https

Hi. I just wanted to notify you that the spacexstats.xyz site does not work with https. It looks like there's a problem with your certificate setup, rather than simply not having a cert at all.

Error message in Chrome: ERR_SSL_PROTOCOL_ERROR

Error message in Firefox: SSL_ERROR_INTERNAL_ERROR_ALERT

Next launch display wrong timezone

On the top-right side of Next Launch, it display time in user's local time.
However, it show (UTC) instead of user's time zone.

I think it should display user's timezone in case of user miss the launch.

Next Launch timer too slow

If you open the stats page the launch timer is running a little bit too slow. I had it open for about an hour to track the next launch (Zuma) and it lost about 10 mins so an considerable amount.

I assume the timer initiates once with the time from the api and then runs in the JS on the client and that thread was too slow.

Proposition would be:
a) change the JS on client to avoid this
b) regulary resync with the server (this would also avoid missing a scrub or postponmend during an open window)

I dont know how many people use the page for this pupose so maybe it is a low priority issue.

Payload Customers statistics not adding up correctly

Images attached showing the issue. The number of launches don't match SpaceX numbers. The percentages given add up to 112%.

Add "last updated" indicator

There is no information when the page was updated.

Upcoming launches

Add upcoming launches as a tab next to the "next launch" tab add upcoming launches. Its supported by the API already as far as i can tell. (https://api.spacexdata.com/v2/launches/upcoming) I would be willing to help implementing this, although I don't really know a good design for it yet.

Front review

If necessary, i will propose a new Front to better organize data, like :

reduce the "Up next" part which is a VID (very important data) but which takes too much space.
delete all the photos and choose only one, website take a long time to load them.
Others ideas are good to take to gain visibility :)

Wording

Remove "s" in "carbon fibers" for fairings reuse
Add "Local or UTC" for the display time of next launch

Next Launches - Upcoming - UTC date time incorrect

API is giving:

...
{
  "flight_number": 72,
  "mission_name": "CRS-16",
  "mission_id": [
    "EE86F74"
  ],
  "launch_year": "2018",
  "launch_date_unix": 1543948680,
  "launch_date_utc": "2018-12-04T18:38:00.000Z",
...

but website is showing:
CRS-16 | Dec 4th 2018, 06:38 | Falcon 9 | CCAFS SLC 40

Note the 06:38 should be 18:38

Possibly wrong number of launches from Boca Chica

Does the Starhopper 150m flight count as a launch. If it does, it should say 1 launch out of Boca Chica.

	updateTimer = () => {
	const factor = this.props.type === 'countdown' ? -1 : 1;
	this.duration = this.duration + factor;

	let secondsLeft = this.duration;
	const days = Math.floor(secondsLeft / (60 * 60 * 24));
	secondsLeft -= 60 * 60 * 24 * days;
	const hours = Math.floor(secondsLeft / (60 * 60));
	secondsLeft -= 60 * 60 * hours;
	const minutes = Math.floor(secondsLeft / 60);
	secondsLeft -= 60 * minutes;
	const seconds = Math.floor(secondsLeft);

	this.setState({
	days: days,
	hours: hours,
	minutes: minutes,
	seconds: seconds,
	});
	}

r-spacex / spacexstats-react Goto Github PK

spacexstats-react's People

Contributors

Stargazers

Watchers

Forkers

spacexstats-react's Issues

Recommend Projects

Recommend Topics

Recommend Org

Jobs