Recommended Posts

They aren't strictly aerodynamic parts - they are the camera mountings. As far as I know, the teams can choose to mount them anywhere they like on the nose, so in their case they've decided to put them right at the front.

Oh yeah I had forgotten about the camera mountings. I thought they had to be as small as possible and have no impact on aerodynamics. There must be a reason they have stuck them out there right on the front. It must make a difference to the aerodynamics. I wonder if there will be some controversy about this.

Ah that makes more sense about the noses. I suspect then that McLaren is the only ones who have a thin enough bulkhead ready then. The others are waiting until the have to do it. I guess the benefits of more air going underneath outweighs it hitting the step. Unless the other teams couldn't redesign their bulkheads and suspensions in time for this season and are having to do the best with what they have.

Oh yeah I had forgotten about the camera mountings. I thought they had to be as small as possible and have no impact on aerodynamics. There must be a reason they have stuck them out there right on the front. It must make a difference to the aerodynamics. I wonder if there will be some controversy about this.

Ah that makes more sense about the noses. I suspect then that McLaren is the only ones who have a thin enough bulkhead ready then. The others are waiting until the have to do it. I guess the benefits of more air going underneath outweighs it hitting the step. Unless the other teams couldn't redesign their bulkheads and suspensions in time for this season and are having to do the best with what they have.

I think the camera mountings are a standard shape/size. If you look at the one located on the Sauber's engine cover, it appears to be the same. Last year's Red Bull had them right at the end of the nose as well: http://www.racecar-e...011/01/RB7a.jpg

From what I understand of the reasoning on the noses, you are right. As McLaren were close to 2012 legal it was a question of lowering the nose by a few centimetres - plus the rest of the car was already designed around a low nose so it isn't a big deal. Everyone else would need to lower the nose considerably, which would require a complete redesign of the whole car as they're based around this high-nose concept.

I still can't get my head around how unrefined the step on the Ferrari's nose looks though...

I think the camera mountings are a standard shape/size. If you look at the one located on the Sauber's engine cover, it appears to be the same. Last year's Red Bull had them right at the end of the nose as well: http://www.racecar-e...011/01/RB7a.jpg

I think I must have just been subconsciously filling those away before. Must be the new nose designs making them look more prominent because they are so thin. Just doesn't look like they are the exact same pods on all the cars. Even though they have to be.

BBC has a good analysis of the McLaren and the difference between it and the step noses.

but yeah as fourjays has said it is to do with a regulation change and airflow...the the reg is not just for a T-Bone impact its also to try and stop cars climbing ontop of another like Webber did.

http://www.bbc.co.uk/sport/0/formula1/16864721

BBC has a good analysis of the McLaren and the difference between it and the step noses.

but yeah as fourjays has said it is to do with a regulation change and airflow...the the reg is not just for a T-Bone impact its also to try and stop cars climbing ontop of another like Webber did.

http://www.bbc.co.uk...rmula1/16864721

Interesting take on it. I hope he is wrong and the McLaren does make a difference. Be nice to see someone else leading the pack instead of everyone following Red Bull.

Red Bull is the most interesting car so far, aside from the McLaren. Here is a good picture of the inlet on the nose:

rbrnose3.jpg

There is a rule against holes right through the nose (was mentioned on Twitter this morning in relation to a hole on the top of the Sauber's nose), although I'm not sure about channels going right through the car (I'd expect so, otherwise it would have been done already). The only hole allowed is a single hole for driver cooling - which this could be. There is a drawing of the Red Bull without a hole in the nose tip, but I can't find any photos to confirm that.

Interesting whatever it is about.

Edit:

No its either an aero trick to keep the flow attached to the nose or the driver cooling inlet

- Tweet by Scarbs (respected F1 tech journalist).

Newey on the RB8:

The restriction nose height which is a maximum height just in front of the front bulkhead hasn?t really changed the chassis shape very much. We?ve kept more or less the same chassis shape, but had to drop the nose just in front of the front bulkhead, which, in common with many other teams, has led us to I think I?d probably say a slightly ugly looking nose. We?ve tried to style it as best we can, but it?s not a feature you would choose to put in were it not for the regulation.

Doesn't sound positive for the stepped noses.

The bull duct is for driver cooling according to Newey

via RacecarEngineer on Twitter, retweeted by Scarbs

So, morning test is over and Raikkonen is top. First time on the Pirellis for him so quite possibly pushing a bit to get used to the tyres. Interesting to see him top though.

Pos Driver Team Time Laps

1. Kimi Raikkonen Lotus-Renault 1m19.670s 50

2. Paul di Resta Force India-Mercedes 1m19.772s 52

3. Nico Rosberg Mercedes 1m20.219s 56

4. Daniel Ricciardo Toro Rosso-Ferrari 1m20.694s 40

5. Mark Webber Red Bull-Renault 1m21.474s 8

6. Kamui Kobayashi Sauber-Ferrari 1m21.534s 29

7. Jenson Button McLaren-Mercedes 1m22.402s 22

8. Felipe Massa Ferrari 1m23.056s 51

9. Heikki Kovalainen Caterham-Renault 1m23.178s 32

10. Pastor Maldonado Williams-Renault 1m23.371s 23

11. Pedro de la Rosa HRT-Cosworth 1m24.322s 16

via Autosport

Raikkonen leads Di Resta on first day of Jerez test

Kimi Raikkonen got his F1 comeback off to a positive start as he set the quickest time in testing at Jerez.

Raikkonen ran a series of rapid laps in the morning culminating in a 1?19.670 which put the Lotus E20 at the top of the times.

Paul di Resta came closed to deposing him with a best effort just a tenth of a second slower in the new Force India.

As always, the headlines times should not be taken as a simple reflection of who?s quickest and who?s slowest. For example, HRT (running last year?s car) were only 5% slower than the fastest time, well below the 7-8% range typically seen in last year?s races.

With nine new cars in action on the first day of the test some teams had comparatively quiet days.

Mark Webber got the year off to a slow start for defending champions Red Bull. He was unable to run during the first few hours of the session as fog at the track delayed the arrival of parts for the new RB8.

Heikki Kovalainen logged 28 laps in the new Caterham CT01 but his day?s running came to an end when the car?s starter developed a fault.

Another driver whose test ended early was Daniel Ricciardo. A drop in oil pressure on his Toro Rosso STR7 caused him to pull over with just over half hour remaining, causing the first red flag of the day.

?We had a very productive morning, doing over 40 laps and we made good progress with our programme,? said Ricciardo.

?Then in the afternoon, we did a couple of longer runs, but had to cut it short, although we only lost an hour. I was using the medium tyre on that last run, having used hard tyres for the rest of the day.?

Meanwhile Kamui Kobayashi, who had shaken down the Sauber C31 yesterday, did over 100 laps in the new car today. But he hit trouble with less than half an hour left in the session, bringing the red flags out a second time.

A brief restart gave Pedro de la Rosa time to post the final improvement of the day in last year?s HRT, before the chequered flag brought the first official test day of 2012 to an end.

Jerez test times

post-1302-0-40008500-1328630926.png

Source: F1 Fanatic

This topic is now closed to further replies.
  • Posts

    • Ladybird Browser is no longer accepting outside contributions thanks to AI by David Uzondu The Ladybird Browser Project has announced it will no longer accept public pull requests and will limit changes to those made by its maintainers as it works towards its first alpha release. According to Ladybird's creator Andreas Kling, this is "not a change we make lightly," but the rapid shift in AI capabilities forced their hand. Previously, a massive PR implied that the person behind it put a lot of care into the code and is ready to "answer for the consequences." Now with AI, anyone can generate a PR without even understanding the bug fix or feature they want merged. The blog post goes on to say that the team is closing all open public pull requests immediately, and that maintainers will not treat external forks as a review queue for upstream Ladybird. Instead, the team wants outside contributors to focus on reporting bugs and running tests. Kling started Ladybird back in 2019 as LibHTML, a simple HTML viewer for his hobby operating system, SerenityOS, but by September 2022, it had turned into a full-fledged browser project. What sets Ladybird apart from the likes of Google Chrome, Apple Safari, or Mozilla Firefox is its totally independent engine, which does not rely on pre-existing codebases. The project maintains a strict policy against default search engine deals or user data monetization, keeping development funded entirely by donations and sponsorships. Generative AI is forcing open source project maintainers to rethink how they handle public code contributions (and the whole open-source thing in general). One month ago, a leak about the National Health Service (NHS) suggested the organization was planning to take all of its public repositories private ahead of a May 11 deadline, thanks to Mythos (an AI model that Anthropic believes is too dangerous to be released to the public) and its ability to find and write exploits for zero-day vulnerabilities. Thankfully, the Government Digital Service (GDS) issued a counter-report titled "AI, open code and vulnerability risk in the public sector" that stopped the shutdown by pointing out that hiding code does not improve security.
    • Kalmuri 4.2.4 by Razvan Serea Kalmuri is your all-in-one, portable screen capture and recording solution designed for speed, simplicity, and flexibility. Whether you need a full-screen snapshot, a custom area, a scrolling webpage, or smooth video recording, Kalmuri delivers with ease. Capture text instantly from images with built-in OCR, keep floating images on top for quick reference, and use the precise color picker for perfect design matching. Customize hotkeys to work your way and share results instantly with built-in upload options. Kalmuri runs without installation, making it ideal for USB use, and offers an intuitive interface that’s easy to learn. Kalmuri key features: Video recording support (designation of whole screen and area) Whole screen, active program, window control, area application Extract text from images using optical character recognition (OCR). Support for PNG, JPG, WEBP, BMP, GIF file formats MP4 video recording powered by FFmpeg for high-quality results Full web page capture Share the captured image on the web Color extraction function Printer output Hotkey settings Adjustable via keyboard for area capture (Arrow key, Ctrl+Arrow key, Shift+Arrow key) File name format (sequential, datetime) Free to use it at work, at home, in government offices, at school, etc. Using Kalmuri portable for video recording Kalmuri’s portable version doesn’t include FFmpeg, which is required for video recording. Without it, you’ll get an “error FFmpeg.exe not found” message. To fix this, download FFmpeg from the provided link, extract it, and place FFmpeg.exe in Kalmuri’s folder. Kalmuri will then recognize it automatically, allowing you to start recording in high quality instantly. Kalmuri 4.2.4 changelog: Fixed an issue where color picking could occasionally freeze Improved capture stability Resolved a possible unexpected app shutdown in certain cases Refined internal handling for a smoother experience Download: Kalmuri 4.2.4 | 24.2 MB (Freeware) Download: Kalmuri Portable 4.2.4 | 2.1 MB View: Kalmuri Website | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • I like the show more options. The only problem with it is that it's not always in a consistent spot in the menu. If the copy/paste/cut, happens to show on top, then more option is the last in the menu. But if copy/paste/cut happens to show on the bottom, then more options is before the copy/paste/cut. But I do like the more options because it hides the stuff that I rarely use. But I would like to choose what it is or isn't hiding. That would make it better.
    • I wonder if "put it back the way it was for decades" ever crossed their minds? 🤣
    • Rescind the stupid "Show more options" in context menus and just give us the full menu instead of adding more steps to get to what we want. The "simpler by default" makes me think they'll go in the opposite direction. Every context menu should have a configure button so you can pick and choose what options should be shown, I know you can do that with some registry fu but that shouldn't be required.
  • Recent Achievements

    • Week One Done
      I2D earned a badge
      Week One Done
    • Week One Done
      Dr Jared Dental Studio earned a badge
      Week One Done
    • Week One Done
      RG INVESTMENT GROUP earned a badge
      Week One Done
    • Very Popular
      The Norwegian Drone Pilot earned a badge
      Very Popular
    • Very Popular
      s0nic69 earned a badge
      Very Popular
  • Popular Contributors

    1. 1
      +primortal
      474
    2. 2
      PsYcHoKiLLa
      250
    3. 3
      Skyfrog
      81
    4. 4
      FloatingFatMan
      64
    5. 5
      Michael Scrip
      62
  • Tell a friend

    Love Neowin? Tell a friend!