153 karma · joined December 30, 2014
Throwing hotel, casino and residential towers on public land isn't about serving the wider community.
http://www.smh.com.au/comment/barangaroo-is-more-insult-than...
It's not going to cause a problem. The uber robot can auto-claim on its robo-insurance which is less than regular insurance because they don't crash as much. They just have to wait around for their auto tow truck who is having a crazy busy week.
Dunno but I will be stealing the tyres off Auto-Ubers to make my tyre shack/mansion in shanty town.
Can't afford Uber? Just hang onto the roof of one.
I thought the point of all this is to have open-source implementations for people to use in their SoCs.
My SoC verification projects have been SystemVerilog only so I am not that familiar with SystemC.
Although I believe SystemC can be used for verification, my concern would be how well it performs in simulation together with SystemVerilog components.
Whenever you mix two different languages it usually runs slower. SystemVerilog is already not fast but you are stuck with it since a lot of IP is in SystemVerilog.
Also splitting the verification environment into SystemC and SystemVerilog for different parts would mean the various metrics like coverage from both sides would have to be merged somehow. It would be a challenge to put it lightly I reckon.
However, if I put my business hat on and am preparing to bid on a project, I find myself without a strong argument for favoring RISC-V instead of ARM or MIPS.
I think I agree with you on that. It is still early days for RISC-V and it would be a big risk to use the core in an SoC now. Every time I take a look at it as an SoC engineer I see a lot of work that needs doing to integrate it.- Basically you would be using a heap of dev tools that you never touched before.
- The bus is something called TileLink which is their own protocol so all your peripherals have to be compatible or wrappers have to be made.
- Verification IP seems minimal and not SystemVerilog so you'd have to write it all yourself.
- Your SW guys would need a good emulator. Don't know if theirs is any good.
Other posts are going on about features but if I think about how much SoC work would be required I question whether it is cheaper than ARM or MIPS.
The jobs have to be something that can't be automated yet still meaningful. My suggestion is make new jobs in politics. More robots means more political arguments over how to govern them.
They should create extra political positions whenever there is an unemployment problem. It would be just like work but you don't have to produce anything. You just argue amongst yourselves. Make new laws. Repeal old laws. It's very social too.
https://en.wikipedia.org/wiki/Bulbasaur
Wikipedia has righted the wrong eventually.
However the creation of the verification testbench and tests is as extensive as the design. The verification team has to work in parallel with the design team so they have enough time to get things done. If they make a mistake in verification it can still also cost a fortune.
If the testbench and tests are not well designed then you are screwed in a roundabout way because the ability to quickly find the bugs isn't there. The testbench has to work on both the rtl and the back annotated netlist.
Approximately 75% of the person-months and compute resources for most projects is verification work. I have been verification lead on multiple projects and design lead on multiple projects. In either role I always looked to assign verification resources as top priority because the project is screwed without it.
On the original topic: The problem is that most commenters are not in the verification field. They don't know the amount or type of work done in verification or the commercial tools involved. This is done in SystemVerilog to do UVM - Universal Verification Methodology. It is not just Verilog. People here are concerned with ease of design. The bottleneck in the industry is in ease of verification.
A negative attitude coming from the parent can really upset the child and they won't learn anything from it.
As a coach I can't tell a parent what to say to their kid at home after they have a poor performance but I usually advise them to try cheer their kid up not cut them down.
It is my role as coach to provide the objective criticism not the parent's. It matters where the criticism comes from.
This is a part of the problem with the original article. Parents are too emotionally involved to teach their kids. They think their kid is special and then they constantly compare them against other kids and then they put the parental pressure on to the child. It isn't helping.
I don't allow parents to do the "tiger mode" criticism on the sidelines because it is not objective. The parents have emotional investment in winning.
I think the point is : It is not really up to the parents to be so critical of their kids. They should be supportive and positive.
It is really up to the coach to provide the technical feedback and it is more beneficial to assess performance at the next practice when the kids are back in a learning mode.
At that point they are mentally ready to practice over their problem areas straight away.
Parents can set their kids back by berating them at the wrong time.
Processes like:
establishing formal communication methods with others in the company - document your plans and decide who needs to read them. Review each item of work completed via a report.
Monitoring the performances of yourself and others objectively. Peer review is crap.
Risk management methods. You have to risk assess as part of planning. Then you monitor whether the risk has eventuated throughout execution of plan.
Quality control processes. Your work must improve stuff. What is the measure of improvement?
What is the explanation? "Rest of team despise Mary" does not cut it.
What sort of upgrade plan that was done 3 months in advance has zero contingencies? How do you know who could become unavailable for some reason?
Then he blames the employee for asking for leave. If you can't handle 1 person being unavailable, you are a bad manager. What if they got sick? You don't cancel.
Bad Management say they make plans all the time. Make proper plans that can adapt to risks. This is real management.
SysAdmin is crucial most tech companies. It is like the engine room. The manager has to be solid as a rock dependable. I don't care about their emotions or their staff. The customer's emotions is the priority if anything.
Professional management means tracking your issues in a way that your superiors can assess your performance. They don't need a bitchfest.
Use an issue tracker. Each issue needs a one line professional description not a soap opera script. You need to assess the impact of the problem and assign a priority to it. You list who is involved in the issue. You create actions for yourself or others and then record the outcomes.
It is your job to find solutions. If there were never any problems and everything ran smoothly, you would be redundant. A lot of management are redundant because they can't solve any issues!
The maturity of management is what makes a company last a few decades rather than a few years. They have to operate professionally, following formal processes to hopefully make objective decisions.
The OP sounds devoid of objectivity and professionalism. If you want to emote you can write in your personal journal. When you go to a management meeting they don't want to see you cry about stuff. They need visibility of the issues and actions.
I actually coach kids from ages 6 - 12 in Judo but team sports can be good also. It's rewarding to see kids mature mentally through training in sports. I have had some real problem kids improve their behaviour over time.
Once they get to about 6, they are mentally ready to learn an organized sport and the challenge is good for them.
The reason management doesn't care is that it isn't important. If a bug eventuates on a web page, the impact is minimal usually.
There are contingencies if a FAQ page is blank like in the article example. The user can visit the contacts page and email their question. Crisis averted.
Most of this web stuff is relatively trivial in terms of impact.
I used to work in ASIC development where the impact of a bug is massive. Hence the verification effort and rigor should be much higher.
Yeah, waveforms from a logic analyzer are mimicked by simulator tools.
Not sure about free references. Just googling around I found this about using logic analyzers : http://www.eetimes.com/document.asp?doc_id=1274572
For example, page 3 shows a RAM timing diagram. Like any good spec, the interface from one module to another is defined via a timing diagram. We build our UVM checkers and monitors to detect these memory transactions based on the sequences specified. When a transaction occurs it triggers a UVM event which in turn can be observed by other monitors/checkers or it can create other events or record the event to a log file etc.
We build our verification infrastructure to automatically check transactions behave as specified. However knowing I can't trust my own work, I manually check the waveforms to see whether the infrastructure is performing correctly.
"Let's just say it's easier to parallelize stuff if one doesn't force their implementation to be inherently sequential or even tied to CPU's."
Sounds interesting. I don't know much about how it's all implemented in the simulator.