Recommended Posts

@primexx: They're the same, the only confusion starts when people use / for fractions ie on the internet, if I wrote 1/2*3, it should be seen as (1/2)x3 (by some logic I guess, at least what I learned in school), but some people use it in a way to describe this fraction:

1

--

2*3

And the only correct way of writing this fraction in one line is: 1/(2*3).

So, to clarify it once and for all, the formula in the post title reads:

48

-- * (9+3)

2

And the only correct solution is 288.

Anyway, I read both / and ? as DIVISION, and as such, it applies only to the digit right of it, unless specified differently by brackets.

@primexx: They're the same, the only confusion starts when people use / for fractions ie on the internet, if I wrote 1/2*3, it should be seen as (1/2)x3 (by some logic I guess, at least what I learned in school), but some people use it in a way to describe this fraction:

1

--

2*3

And the only correct way of writing this fraction in one line is: 1/(2*3).

Well yeah, but here you don't have the problem of the juxtaposition.

1/2*3 should be solved by writing each factor between brackets like this:

(1)*(1/2)*(3).

It's just the juxtaposition that has multiple interpretations depending on what convetions you learned that is causing the problems.

@primexx: They're the same, the only confusion starts when people use / for fractions ie on the internet, if I wrote 1/2*3, it should be seen as (1/2)x3 (by some logic I guess, at least what I learned in school), but some people use it in a way to describe this fraction:

1

--

2*3

And the only correct way of writing this fraction in one line is: 1/(2*3).

So, to clarify it once and for all, the formula in the post title reads:

48

-- * (9+3)

2

And the only correct solution is 288.

Anyway, I read both / and ? as DIVISION, and as such, it applies only to the digit right of it, unless specified differently by brackets.

Good points, indeed.

Now I'm unsure again.

PEMDAS. Order of operations.

Parenthesis/Exponents/Multiplication/Division/Addition/Subtraction

Zzz... Read last two pages. Multiplication does not have priority over Division (and the other way around). Same goes for addition and substraction.

Good points, indeed.

Now I'm unsure again.

he's right, but it doesn't address the original point of the juxtaposition convention, which Ambroos correctly identifies as the point of difference.

I still maintain that multiplying any arbitrary term by 1 should not result in a different answer, and if a rule of precedence results in a discrepancy, then the rule is demonstrably flawed.

edit: at least we can all agree that the people citing mnemonics in the exact order need to RTFT :p

he's right, but it doesn't address the original point of the juxtaposition convention, which Ambroos correctly identifies as the point of difference.

I still maintain that multiplying any arbitrary term by 1 should not result in a different answer, and if a rule of precedence results in a discrepancy, then the rule is demonstrably flawed.

edit: at least we can all agree that the people citing mnemonics in the exact order need to RTFT :p

His beginning premise was wrong, if you look at the formula the way I've written it (and the correct way), he can't possibly multiply (9 +3) with 2, therefore multiplying anything by 1 doesn't change the end result in no way whatsoever -- which is one of the basic things we learn in math.

I still maintain that multiplying any arbitrary term by 1 should not result in a different answer, and if a rule of precedence results in a discrepancy, then the rule is demonstrably flawed.

I agree with you that it shouldn't, but that's the exact problem of conventions. Not everyone follows them, they're not mathematically correct and they only apply to strict situations that would otherwise not be possible to be solved... Conventions are basically just incorrect rules that exist to solve the unsolvable...

His beginning premise was wrong, if you look at the formula the way I've written it (and the correct way), he can't possibly multiply (9 +3) with 2, therefore multiplying anything by 1 doesn't change the end result in no way whatsoever -- which is one of the basic things we learn in math.

i don't think he began with the premise that the division symbol encapsulated everything following it. he was arguing that some little known rule of precedence (which I've demonstrated to be stupid by now) requires you do the number beside the bracket first, which of course is ridiculous especially with the way you wrote the formula.

I agree with you that it shouldn't, but that's the exact problem of conventions. Not everyone follows them, they're not mathematically correct and they only apply to strict situations that would otherwise not be possible to be solved... Conventions are basically just incorrect rules that exist to solve the unsolvable...

that's a rather strict definition of what it is to be "correct", but of course conventions are not laws.

We have this convention in high school that for ambiguous terms, if you mean to have a parenthesis in it then put it. Otherwise no parenthesis means there shouldn't be one there. So in this case if you mean to divide 48 by 2 should put (48?2)(9+3)=288. But since there's no parenthesis so the answer is 2.

We have this convention in high school that for ambiguous terms, if you mean to have a parenthesis in it then put it. Otherwise no parenthesis means there shouldn't be one there. So in this case if you mean to divide 48 by 2 should put (48?2)(9+3)=288. But since there's no parenthesis so the answer is 2.

Actually I think that's backwards. If you don't assume parentheses* around the 2(9+3) then what you actually have is 48 / 2 * 12, which evaluates to 288. In order to get 2 you have to assume parentheses*, so 48/(2(9+3)) which is 48/24, or 2.

* And by assume parentheses I mean treating a distribution as higher presidence than normal multiplication, which is the main argument in this thread.

Actually I think that's backwards. If you don't assume parentheses* around the 2(9+3) then what you actually have is 48 / 2 * 12, which evaluates to 288. In order to get 2 you have to assume parentheses*, so 48/(2(9+3)) which is 48/24, or 2.

* And by assume parentheses I mean treating a distribution as higher presidence than normal multiplication, which is the main argument in this thread.

I'm talking about parenthesis around 48/2. The convention in parentheses is on top of juxtaposition precedence. If it seems ambiguous this is how we resolve it. The need to put parentheses in the denominator comes when the denominator is composed of addition elements. e.g. 48/[2(9+3) + 18 + 6] = 1 whereas 48/2(9+3) + 18 + 6 = 26.

If you didn't put parentheses then it's not meant to be there, on top of other conventions/rules. If I meant (48/2)(9+3) I would have written 48(9+3)/2.

48?2(9+3)

48/2*(9+3)

48/2*(12)

48/2*12 because (12) evaluates to 12

24*12

288

Very tricky question. It doesn't help that ? looks like +. Anyway, it's pretty obvious if you do some manipulations. For instance:

X = (9 + 12);

Y = 48/2*X;

Obviously the value of Y would be 288 because the order of operations are more clear.

Or if you represent it as a fraction as you would on paper:

48

--- x (9 + 3) = 48(9+3)/2 = 288

2

Look, this isn't a difficult problem. If you don't believe that the answer is 288, try typing it into a calculator. Write a program in any programming language. Try WolframAlpha.

http://www.wolframalpha.com/input/?i=48%2F2%289%2B3%29

You are making this WAY more difficult than it really is.

If you can't solve this problem, you also will have trouble with problems like this: 1/2((3/4)5)/6 = 5/16

Actually I think that's backwards. If you don't assume parentheses* around the 2(9+3) then what you actually have is 48 / 2 * 12, which evaluates to 288. In order to get 2 you have to assume parentheses*, so 48/(2(9+3)) which is 48/24, or 2.

* And by assume parentheses I mean treating a distribution as higher presidence than normal multiplication, which is the main argument in this thread.

Do you need to distribute in order to solve the expression in parentheses?

If so then the very first expression that is calculated by priority of Parentheses is 2(9+3) or (2 x 9 + 2 x3). The fundamental question is can the 9 and 3 be added together without factoring in the 2?

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • 150.0.4078.65 secret changelog: New feature: Settings > Copilot and AI > Allow Cowork to take actions on your behalf
    • OBS Studio 32.2.0 RC1 by Razvan Serea OBS Studio is software designed for capturing, compositing, encoding, recording, and streaming video content, efficiently. It is the re-write of the widely used Open Broadcaster Software, to allow even more features and multi-platform support. OBS Studio supports multiple sources, including media files, games, web pages, application windows, webcams, your desktop, microphone and more. OBS Studio Features: High performance real time video/audio capturing and mixing, with unlimited scenes you can switch between seamlessly via custom transitions. Live streaming to Twitch, YouTube, Periscope, Mixer, GoodGame, DailyMotion, Hitbox, VK and any other RTMP server Filters for video sources such as image masking, color correction, chroma/color keying, and more. x264, H.264 and AAC for your live streams and video recordings Intel Quick Sync Video (QSV) and NVIDIA NVENC support Intuitive audio mixer with per-source filters such as noise gate, noise suppression, and gain. Take full control with VST plugin support. GPU-based game capture for high performance game streaming Unlimited number of scenes and sources Number of different and customizable transitions for when you switch between scenes Hotkeys for almost any action such as start or stop your stream or recording, push-to-talk, fast mute of any audio source, show or hide any video source, switch between scenes,and much more Live preview of any changes on your scenes and sources using Studio Mode before pushing them to your stream where your viewers will see those changes DirectShow capture device support (webcams, capture cards, etc) Powerful and easy to use configuration options. Add new Sources, duplicate existing ones, and adjust their properties effortlessly. Streamlined Settings panel for quickly configuring your broadcasts and recordings. Switch between different profiles with ease. Light and dark themes available to fit your environment. …and many other features. For free. At all. OBS Studio 32.2.0 changelog: Release Candidate 1 Changes Fixed empty name label in volume meter in Beta 1-3 [Warchamp7] Fixed macOS Audio Capture sources capturing cursors unnecessarily [jcm93] Beta 3 Changes Fixed extra padding on some UI elements on Windows in Beta 1-2 [Warchamp7] Fixed NVIDIA Audio Effects not working in Beta 1-2 [pkviet] Fixed issues with long item names in the Audio Mixer in Beta 1-2 [Warchamp7] Removed redundant "Monitor Only" from the Advanced Audio Properties window [Warchamp7] Mute and Monitor are handled independently in the new Audio Mixer Removed Close button from What's New dialog [Warchamp7] Removed margins from What's New dialog [Warchamp7] 32.2 New Features Replaced add source dropdown with new dialog [Warchamp7] Improved FPS selector UX [jcm93] Added missing file support for filters [exeldro] Added ability for plugins to set custom icons for new source types [cg2121] Included .webp files when adding a directory to Image Slide Show source [TarunCore] Added copy paste functions to frontend API [exeldro] Added filter to compose SDR into HDR [jpark37] Added delete as a hotkey to delete sources on macOS [PatTheMav] Added dynamic bitrate support to multitrack video [lexano-ivs] 32.2 Changes Forced Intel-based installations to update to Apple Silicon version on macOS [PatTheMav] This change means that OBS Studio versions built for Intel-based Macs but running on Apple Silicon Macs will automatically update to OBS Studio built for Apple Silicon Macs. If an installation was using third-party plugins, those plugins will no longer load until replaced with Apple Silicon versions. Fixed audio mixer state getting out of sync when changing settings via websockets or plugins [Warchamp7] Added theming for checked QToolButtons [glikely] Improved OpenGL performance slightly on low-end machines [kkartaltepe] Set minimum size for color source to 1 pixel [exeldro] Added minimum width to spinboxes [Warchamp7] Disallowed overwriting the crash handler [sebastian-s-beckmann] Applied process mitigation policies for Windows [notr1ch] Adjusted description of multitrack video [jhnbwrs] Changed new capture devices to use fallback frame rate by default [PatTheMav] Improved DLL loading behavior on Windows [notr1ch] Limited multitrack video config to Custom service [PatTheMav] 32.2 Bug Fixes Fixed OAuth and dock state save corruption [PatTheMav] Fixed group bounds not resizing when removing items [howellrl] Fixed canvas mixes not being restored after video reset [dsaedtler] Fixed some erroneous crashes during shutdown [Warchamp7] Fixed display capture sometimes capturing black after a duplicator failure [ThrowTop] Fixed color of controls dock output buttons in System theme [shiina424] Fixed virtual camera reset failures [stephematician] Fixed potential crash when user discards changes in the settings window [suogesi] Fixed incorrect return value in virtualcam filter [xtfo] Fixed source toolbar buttons not working after dragging a source into a group [Warchamp7] Fixed properties hint icon spacing [Warchamp7] Fixed potential crash when a video device reconnects on macOS [jcm93] Fixed an issue where PipeWire could fail on NVIDIA GPUs [hoshinolina] Fixed obs_canvas_get_video_info returning incorrect framerate [dsaedtler] 32.2 Deprecations Deprecated obs_properties_add_button [sebastian-s-beckmann] Download: OBS Studio 32.2.0 RC1 | Portable | ARM64 | ~200.0 MB (Open Source) View: OBS Studio Homepage | Other Operating Systems | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • For real. Forums are about as social media as I’ll ever get.
    • Lexar PLAY X 1TB 2230 review: blazing fast PCIe Gen4x4 gaming SSD for PC and consoles by Steven Parker Lexar reached out to us asking if we were interested in taking a look at the Lexar PLAY X SSD. This drive is mostly (but not strictly) intended for handhelds and consoles as a means to expand storage for gaming, but you can use it however you like. In our case we were sent the 2230 1TB variant, so we plopped it into the bracket that's included in the box and installed it in our test PC. Before we get underway, Lexar provided a free sample without any editorial input or review pre-approval. Below are its specifications: Lexar PLAY X Interface PCIe Gen4x4 with NVMe Form Factor M.2 2030, M.2 2230, M.2 2280 Capacity 512GB, 1TB, 2TB Speed 512GB: Sequential read speed up to 7200MB/s, sequential write speed up to 4500MB/s, random read up to 900K IOPs, random write up to 900K IOPs 1TB: Sequential read speed up to 7400MB/s, sequential write speed up to 6400MB/s, random read up to 1000K IOPs, random write up to 1000K IOPs 2TB: Sequential read speed up to 7400MB/s, sequential write speed up to 6500MB/s, random read up to 1000K IOPs, random write up to 1000K IOPs DRAM Cache No TB written 512GB: 300TBW, 1TB: 600TBW, 2TB: 1200TBW Operation temp 0° to 70°C (32°F to 158°F) Storage temp - 40° to 85°C (- 40°F to 185°F) Durability Shock Resistance: 1500G, duration 0.5ms, Half Sine Wave Vibration resistenence: 10~2000Hz, 1.5mm, 20G, 1Oct/min, 30min/axis (X, Y, Z) MTBF 1,500,000 Hours Dimensions 80 x 22 x 2.45 mm / 3.15”x0.87”x0.10” Weight 9.5g / 0.02lbs Part nr LNMPLYX001T-RNNNG Warranty 5 years Price £119.99, €119.99, / £218.99, €249.99 First a few notes about the specs. The Lexar PLAY X SSD does not come with a (graphene) heatsink so you will have to ensure you have a thermal pad or something that can be used with this drive, and secondly it says in the specs that it does not have a DRAM Cache, as it makes use of: Basically what this means is that HMB handles finding files, while the Dynamic pseudo-SLC cache handles writing them. The Lexar PLAY X uses TLC NAND flash memory, which stores three bits of data per cell. Writing three bits requires checking multiple voltage levels, which takes time. It's a trade off for the drive size too, as it would be difficult to place DRAM cache onto the 2230 format. What's in the box Lexar PLAY X (1TB) 2280 Bracket 2230 and 2280 Sticker Quick Installation Guide Our test system consists of the following: Lian Li O11 Dynamic Mini V2 Flow (Amazon|Newegg) ASUS ProArt Z890-CREATOR WiFi (Amazon|Newegg) Intel Core Ultra 7 270K Plus (Amazon|Newegg) Thermal Grizzly KryoSheet - 44x37 (Amazon|Newegg) 2x 16GB G.Skill Trident Z5 RGB (7200 MT/s in XMP) (Amazon|Newegg) Sabrent Rocket4 Plus 2TB SSD (Amazon) Windows 11 Pro 25H2 (Build 26100.8655) Benchmarks With that out of the way, we ran some benchmarks comparing (historic) data with a couple of other drives on a system that is up to date with the latest June Patch Tuesday updates. Aside from the clear difference between the PCIe 4x4 and PCIe 5x4 results, it is also clear that applying correct thermal conditions, in this case the DARK AirFlow I, makes a difference with the outcome of the score as can be seen on the TeamGroup Z540. (hsf = heatsink & fan, hs = heatsink) WD SN850X Lexar PLAY X Z540 with DARK AirFlow I In our 3DMark Storage benchmark test (images above), which measures access times and bandwidth for gaming scenarios, the Lexar PLAY X was the fastest. Even compared to the actively cooled TeamGroup Z540, this one was 23% faster, despite being on PCIe Gen4; and it was doing so while running cool too, as you will see later in our temperature stress test. The Lexar PLAY X supports DirectStorage like other NVMe drives, and here, the SSD was a lot better with DirectStorage enabled on our 3DMark DirectStorage feature test. With GDeflate especially, the improvement is tremendous. Overall, the test result says that the Lexar PLAY X was nearly three times faster while running with DirectStorage. (hsf = heatsink & fan, hs = heatsink) Z540 with DARK AirFlow I Lexar PLAY X WD SN850X Next we ran the default CrystalDiskMark test (images above) and measured the disk temperature. Even with the motherboard M.2 heatsink applied to the top of it, the drive managed to reach a peak of 70C, which is well within specification. Also, another positive is that it exceeded its advertised sequential write speed of 6,400 MB/s in our testing, which is rare and deserves praise. Z540 with DARK AirFlow I Lexar PLAY X WD SN850X The second test is of six passes at 16GB (images above), meant to stimulate a heavier, longer transfer session, and it reached the same max temp of 70~71C. This indicates that the PLAY X is performing exceptionally well even under heavy loads. It is not as chill as the WD_BLACK SN850X, but 70-71 C is completely safe. Usage Although Lexar generally markets anything stamped with "Play" for handhelds and consoles, on the official product page and Amazon listing, the PLAY X is definitely marketed as an all-rounder with the company claiming that it is: This is exactly what we did, as our sample was placed into the 2280 bracket and installed in the M.2_1 slot on our ASUS ProArt Z890-CREATOR WiFi. CrystalDiskInfo Idle temp as shown above is also pretty decent at 28C. Lexar DiskMaster Lexar also provides a disk utility that can read the disk information and benchmark it. S.M.A.R.T info can be viewed above and it loads automatically in the program, I also ran the "Performance testing" which gave a better result than we saw in CrystalDiskMark v9.0.2. Conclusion I have to say I came out very impressed with the PLAY X, especially seeing how well it did in the 3DMark gaming test. That was surprising for sure, in a good way of course. Hence, as the name suggests, the PLAY X can be a great drive for gaming rigs. The drive ran fairly cool as well, although you will want to make sure it's properly cooled, seeing how it was reaching its maximum recommended operating temperature; but there was no noticeable throttling. The 600 TBW rating of the 1TB variant seems pretty good as well for this gaming-orientated storage where writes will be happening more frequently for game saves and what-not, but even so, you should see years of use without any problems and even if you do run into problems, the five year warranty should have you covered. A bit of a downer for our U.S. readers though, Lexar told me that the PLAY X is not yet available to purchase in the United States, but it can be ordered if you're in the UK. I asked when they plan to release it there and was told: In addition, although the initial review documentation and official website suggests there is also a 2 TB variant, Lexar have stated that "The 2TB version has not been launched yet." As you can see from the links below, the 1 TB variant is also selling a bit above the RRP in the UK, and the 512 GB version aligns with Lexar's RRP. Lexar PLAY X 1 TB for £241.99 on Amazon UK Lexar PLAY X 512 GB for £119.99 on Amazon UK We hope the 2TB variant becomes available soon, considering how well the drive did in our game data tests. We feel the higher capacity will be popular for sure, though at this time, the lack of it is not hard to understand why, given the shortage and the shift in focus for a lot of companies. Sayan Sen contributed to this review. As an Amazon Associate we earn from qualifying purchases.
    • This seemed like a fake news story, or AI generated. Nope, apparently true. https://www.bbc.co.uk/news/uk-england-devon-45414022
  • Recent Achievements

    • One Month Later
      pahariyaseo earned a badge
      One Month Later
    • Week One Done
      pahariyaseo earned a badge
      Week One Done
    • Week One Done
      hadiaali45 earned a badge
      Week One Done
    • Week One Done
      arone_24 earned a badge
      Week One Done
    • Reacting Well
      flexorcist earned a badge
      Reacting Well
  • Popular Contributors

    1. 1
      +primortal
      408
    2. 2
      PsYcHoKiLLa
      140
    3. 3
      Nick H.
      89
    4. 4
      +Edouard
      83
    5. 5
      neufuse
      71
  • Tell a friend

    Love Neowin? Tell a friend!