For a while I've been stuck in slow speed mode again, not really doing great work, just being on average. It feels weird. Don't really get much done, but I have on the other hand had a great deal of time to test some "new" technologies, well, new as in only 10-15 years old I guess :-). I'll get back to that later. Also, I've begun a new contract at "a big telecom company".
This is my first time at a really giant hunk of a company, the biggest I've seen before was circa 500 people in all, and it moved slower (the beaurocracy) than this in all honesty. This BigCompany is actually quite interesting to me. Started off with almost 4 weeks of introductions, courses, and so forth. They have a dedicated TEAM of CM's, that alone is just... wow :-P. I've just been put up to speed and started working a little before this weekend so I might be a bit premature, but I like it so far. The weird part is, things actually happen, but not as I'm used to it. I'm used to 13+hour days and frentic coding/hacking to get things to happen, everyone here eschews away with their 8 hour days -- only working overtime at very special occasions -- yet slowly things get done, new functionality gets added and so forth.
Another thing that kind of amazes me -- and worries me to some extent -- is the kind of planning that is done. I'm used to small scale projects with workpackages or task based development, where no workpackage should ever take more than 4-5 days to implement. This place uses a workpackage development structure where each package takes up to 6-7 weeks for 6-10 people to implement. We'll see how it works out -- at least their "stand-up meetings" actually works :-).
All that being said, I had the time to write quite a bit of python which is a first, then I've looked into d-bus architecture which is also a first, and I also looked into Bluetooth and how to use it -- some test applications running, fetching services and graphically displaying info about all units it finds etc. The complexity of Bluetooth is rather saddening imho, it's a horrible protocolstack to work with in some senses, even though I was really impressed by how much python does for you.
I've been unused to the whole concept of python before this, and just a tad sceptical. Mainly because of all the problems with version matching that you always wind up having to do, to make anything work properly (try getting scons, trac and wamp, and some more tools working on a win32 machine some day for some fun).
Anyways, I always figured there has to be an upside, and there really is -- python is hackfriendly :-) . In less than 3-4 hours I went from writing my first simple helloworld to having a scratch written class based graphical (tkinter) interface implementing some very fundamental bluetooth commands. In my world, thats not bad at all ;).
I've also had time to learn a lot of new tools at work. I'll comment on those some other day as I havent seen much other comments on some of them (some is imho very expensive crap with a nice wrappings, while some actually are completely awesome). Sidenote, I simply adore the systems we are working on 4 xeon with 4cores and 64 gig ram.
I'll get back later :-).
torsdag 9 april 2009
torsdag 26 februari 2009
Swedish postal services suck
Just a quick note, Swedish postal services suck. They are completely retarded to deal with. Since christmas, I've ordered 5 packages sent via "Posten", 4 of those are lost/stolen.
I've spent over 8 hours on hold and in phonelines to posten trying to report these different losses etc. If you read this, and use Posten for package delivery, or you are a company sending packages to Sweden, please use another service. A list of the packages that has been lost so far:
1. An Acer Aspire One + extra ram, stolen over 1,5 months ago, still haven't received payment for the laptop. According to my research, it could be up to 4-5 months before they get their thumbs out of their asses and pay money to me.
2. Electronics, it was delivered to package delivery, but i never got notified, and after 7 days it was returned -- packages are supposed to be left for 14-30 days, and you're supposed to get notified. Elfa was kind enough to repay me in full.
3. Cell phone, it was delivered in Alvesta since posten claims it's my closest pickup point. For those not knowing, Alvesta is 300-400km away from me. Again, no notification. No payment done in advance.
4. Replacement cell phone, sent over a week ago. Still no notification, possibly gone?
As you can understand, I'm not happy with the services. The only package that I did receive? It was sent with inWarehouse to their own pickup point, 1,5km extra travel to pick it up, but sooo worth it.
I've spent over 8 hours on hold and in phonelines to posten trying to report these different losses etc. If you read this, and use Posten for package delivery, or you are a company sending packages to Sweden, please use another service. A list of the packages that has been lost so far:
1. An Acer Aspire One + extra ram, stolen over 1,5 months ago, still haven't received payment for the laptop. According to my research, it could be up to 4-5 months before they get their thumbs out of their asses and pay money to me.
2. Electronics, it was delivered to package delivery, but i never got notified, and after 7 days it was returned -- packages are supposed to be left for 14-30 days, and you're supposed to get notified. Elfa was kind enough to repay me in full.
3. Cell phone, it was delivered in Alvesta since posten claims it's my closest pickup point. For those not knowing, Alvesta is 300-400km away from me. Again, no notification. No payment done in advance.
4. Replacement cell phone, sent over a week ago. Still no notification, possibly gone?
As you can understand, I'm not happy with the services. The only package that I did receive? It was sent with inWarehouse to their own pickup point, 1,5km extra travel to pick it up, but sooo worth it.
Off-work robot fun
As of late, I've been having loads of fun with an old robot of mine, Robby RP5. My biggest complaint at all times has been the fact that it has a horrible 8-bit processor with "some kind of" Basic interpreter/compiler that I never quite figured out because it is so boring and ... well, let's face it, you will never be able to do anything "wow" in a language that is more or less assembler having 4k flash and 256bytes ram where only some 60 bytes are actually available.
As of late, we've been having some fun with zigbee modules at work, and I figured out a way to have fun with my old Robby again. Robby has a serial port, and I'm connecting one zigbee module to that one, and on the other end I've got a zigbee module connected to my computer via USB. On the Robby processor, I got a very simple program that simply talks a protocol sent over the zigbee connection and "implementing" the commands sent in packets. There are 3 packets that can be sent, TrackData, SensorData and RequestData. TrackData packet sent from computer sets speed of both tracks individually, RequestData is sent from computer to Robby and contains a request for a packet back. The Request can either be TrackData or SensorData. SensorData contains data from all sensors supported (currently only IR range sensors).
My first demonstration program on the computer is connected to a joystick and simply transforms the joystick input and sends it to the robot. Pushing button 0 requests sensordata and 1 trackdata.
Right now, I'm looking at porting my robot drivers into the Player/Stage project which I've been looking heavily at as of late, and seems damn cool. I've been testing some of the example robots in the Stage simulator, and if I would port my setup into that project, I should be able to use the available robot "behavioural modules" straight on my robot, and/or test my new modules in a simulator before actually running in the real world. In all honesty, I think player/stage is the best thing I've ever found since sliced bread, it simply opens up for sooo much fun :) . Connect this with a couple of zigbee modules, you can build very simple and cheap robots that are extremely powerful. 60ÜSD robot chassis, 5USD processor, 10USD junk, 30USD for 2 zigbee modules, add some sensors, and you've got as much as you can ask for. Robby for example is around 110USD, probably much lower, a pair of zigbee modules are 30USD.
And yes, I will open this once I feel that I'm closer to finished :-).
As of late, we've been having some fun with zigbee modules at work, and I figured out a way to have fun with my old Robby again. Robby has a serial port, and I'm connecting one zigbee module to that one, and on the other end I've got a zigbee module connected to my computer via USB. On the Robby processor, I got a very simple program that simply talks a protocol sent over the zigbee connection and "implementing" the commands sent in packets. There are 3 packets that can be sent, TrackData, SensorData and RequestData. TrackData packet sent from computer sets speed of both tracks individually, RequestData is sent from computer to Robby and contains a request for a packet back. The Request can either be TrackData or SensorData. SensorData contains data from all sensors supported (currently only IR range sensors).
My first demonstration program on the computer is connected to a joystick and simply transforms the joystick input and sends it to the robot. Pushing button 0 requests sensordata and 1 trackdata.
Right now, I'm looking at porting my robot drivers into the Player/Stage project which I've been looking heavily at as of late, and seems damn cool. I've been testing some of the example robots in the Stage simulator, and if I would port my setup into that project, I should be able to use the available robot "behavioural modules" straight on my robot, and/or test my new modules in a simulator before actually running in the real world. In all honesty, I think player/stage is the best thing I've ever found since sliced bread, it simply opens up for sooo much fun :) . Connect this with a couple of zigbee modules, you can build very simple and cheap robots that are extremely powerful. 60ÜSD robot chassis, 5USD processor, 10USD junk, 30USD for 2 zigbee modules, add some sensors, and you've got as much as you can ask for. Robby for example is around 110USD, probably much lower, a pair of zigbee modules are 30USD.
And yes, I will open this once I feel that I'm closer to finished :-).
tisdag 27 januari 2009
Work? What work?
So, just a brief update. I've recently (a few months back *cough*) taken over our Linux "education" group at work, and it's interesting. The sad part is, we mostly only see people who already knows what Linux is as we're working internally in a world where most people are rather Computer savvy as it is. It's given me a few new viewing angles though, and I'll get back to that at a later point.
Currently working on some Trac guidelines for our Change Management process as well. Working from home today to actually get something done with it, as most of the days I wind up getting too many disturbing calls, talks and discussions to be very efficient. Our first two tries at making a decent workflow winded up a bit messy, and I think we really must get this down properly this time.
There are some other things I react on, and want to fix, for example, as it looks now, every single project sets up their own bugtracking/ticketsystem, and every project uses a different system (trac, mantis, clearcase, dimensions, etc). Preferably, this should be centralized in some fashion, and if possible I'd love to get a bit more homogenized environment. As it is, I try to tell people "look, here's a system for handling your day to day tasks, use it!". First time, the workflow got overly complex, second shot was also overly complex, and people where put off by all the choices and steps to take. This problem mainly stems from project/change management criterion.
My latest and greatest (yeah yeah) workflow should alleviate some of these problems by making some of the choices less visible to normal users. Ie, we have one task management system and a problem and change management system baked into one, but normal users (programmers) only use the task management system, while the project manager, tech project manager and CM also have the ability to handle problems and changes in separate workflows.
We're also adding the ability to have supertickets, where a single problem report can contain several tasks. This is a pseudo development so far, as we're not actually adding the whole deal right now, we're just adding the idea of it, not bounds checking or views/reports of it. Basically, every ticket can have a superticket (we add a numeric field to the ticket), which can point to another ticket, which is the "parent" ticket. This makes it possible to handle a large and complex bug in several smaller tickets. Anyways, the idea is there, but it's not fully implemented. If our management likes it, and the others like it, we could implement it for future usage. I'm worried it's too complex however. At the same time, one complex system might be better than 6 alltogether different systems as it allows for longer time to learn? Kind of like... well, unix for example. Once you find ls, its a darn good bit faster than having to click your way through a whole heap of paths to find the specified file list.
At the same time, both me and PM are a bit tired of Trac's shortcomings, maybe change to Mantis for example? My general thought to this however is, we need to stick it out i'm afraid... one more system will just make the normal user less interested in the new tool and hence taking even longer to learn. As it is, people use it at a bare minimum cause they dont know it, give them time to learn it properly, and they might come to like it. Comments on this line of thinking?
For now, tata. Back to writing.
Currently working on some Trac guidelines for our Change Management process as well. Working from home today to actually get something done with it, as most of the days I wind up getting too many disturbing calls, talks and discussions to be very efficient. Our first two tries at making a decent workflow winded up a bit messy, and I think we really must get this down properly this time.
There are some other things I react on, and want to fix, for example, as it looks now, every single project sets up their own bugtracking/ticketsystem, and every project uses a different system (trac, mantis, clearcase, dimensions, etc). Preferably, this should be centralized in some fashion, and if possible I'd love to get a bit more homogenized environment. As it is, I try to tell people "look, here's a system for handling your day to day tasks, use it!". First time, the workflow got overly complex, second shot was also overly complex, and people where put off by all the choices and steps to take. This problem mainly stems from project/change management criterion.
My latest and greatest (yeah yeah) workflow should alleviate some of these problems by making some of the choices less visible to normal users. Ie, we have one task management system and a problem and change management system baked into one, but normal users (programmers) only use the task management system, while the project manager, tech project manager and CM also have the ability to handle problems and changes in separate workflows.
We're also adding the ability to have supertickets, where a single problem report can contain several tasks. This is a pseudo development so far, as we're not actually adding the whole deal right now, we're just adding the idea of it, not bounds checking or views/reports of it. Basically, every ticket can have a superticket (we add a numeric field to the ticket), which can point to another ticket, which is the "parent" ticket. This makes it possible to handle a large and complex bug in several smaller tickets. Anyways, the idea is there, but it's not fully implemented. If our management likes it, and the others like it, we could implement it for future usage. I'm worried it's too complex however. At the same time, one complex system might be better than 6 alltogether different systems as it allows for longer time to learn? Kind of like... well, unix for example. Once you find ls, its a darn good bit faster than having to click your way through a whole heap of paths to find the specified file list.
At the same time, both me and PM are a bit tired of Trac's shortcomings, maybe change to Mantis for example? My general thought to this however is, we need to stick it out i'm afraid... one more system will just make the normal user less interested in the new tool and hence taking even longer to learn. As it is, people use it at a bare minimum cause they dont know it, give them time to learn it properly, and they might come to like it. Comments on this line of thinking?
For now, tata. Back to writing.
söndag 4 januari 2009
Christmas ending
So, christmas and new years holidays is coming to an end. A long and arduous autumn/winter at work has ended, and an equally joyful christmas holiday is ending. This has been the year of working for my part, and the experience has been incredible. In all honesty, I've never had the opportunity to work in such a stimulating environment as I have the last few months, and I'm very happy for it.
Me and the girlfriend had the bad habit of buying an Xbox 360 for ourselfs this christmas, which made us realize we have a really small tv, so within 5 days we bought a new one. Then, we realized how bad speakers we have, so we winded up buying a set of bose speakers and new spdif cables within 2-3 days as well. This in turn, and the fact that I finally had some spare time, lead to me spending a lot of time finally getting the HTPC configured and working.
The entire HTPC is worth mentioning since I've put it together from parts, and installed/configured everything on my own. My opinion is that mythtv and ubuntu (mythbuntu) has come a long way as a platform for end users, but they still have a long way to go I'm afraid. My biggest annoyance is still the same it was 12 years ago unfortunately, and I think it's to some extent become even worse over time. Graphics and Sound drivers...
I personally have fairly new nvidia card which I want 3d graphics on, and all the hardware accelerations etc, in other words I'm stuck with the nvidia drivers. You would think it would be easy with the proprietary hardware drivers stuff in Ubuntu, but it's not. It's actually worse than some years ago when I last handled these setups, then all you had to do was compile and install drivers in the correct kernel modules directory. Now you have to fight with umpteenth other installers which crashes and overwrites eachothers and so forth, and then when you do an update, all of a sudden you overwrite your working drivers with nonworking versions and you're stuck trying to figure out just what happened. Also, the choice of good graphics cards has become smaller imho. If you want something powerful, you're stuck with nvidia or ati. Both drivers are completely horrible to get working. I'm hoping the rumours I've heard lately will turn true here, and we'll finally see better support for open source software from both companies, at least if they could make a single decent installer for the proprietary drivers in the common Linux distributions.
And my final gripe, which isn't so large as the other ones, the sound drivers. Sound was absolutely horrible back in the days with OSS, whatever soundcard I tried to install, I winded up with either having to run the trial OSS drivers, or choosing between no sound and buying the OSS drivers. This has become much better happily. It's still not working flawlessly as I just found out (SPDIF took a few hours to get working, and I still haven't gotten 5.1 output to work correctly over SPDIF).
These are critical areas of an OS (you expect sound and graphics to "work out of the box" these days, not having to screw around with settings/drivers/installers as soon as you deviate by a single micron from the specifications.
On top of this, I had some more serious issues with my iMON PAD remote, once again after reinstalling the system. That I can live with, but it's a serious annoyance. For some reason, the configurations shipped with mythbuntu had a bunch of codes that where off by a few numbers every here and there, and then there was a lot of buttons not connected between lirc to mplayer and mythtv.
Apart from this, I'm very happy with the setup by now. The basic functionality is there, but it's made for tweaking and having fun, so there's still a lot of things I'm interested in doing on it :-).
By now, I'm mainly waiting for work to start again, I feel rested, I've gotten to fiddle with some hardware and software, and I got new energy for the new year. I just need to try and get working on my webpage and stuff like that a little bit more so I can finally finish it. Like all IT projects, it's running very late ;-).
Me and the girlfriend had the bad habit of buying an Xbox 360 for ourselfs this christmas, which made us realize we have a really small tv, so within 5 days we bought a new one. Then, we realized how bad speakers we have, so we winded up buying a set of bose speakers and new spdif cables within 2-3 days as well. This in turn, and the fact that I finally had some spare time, lead to me spending a lot of time finally getting the HTPC configured and working.
The entire HTPC is worth mentioning since I've put it together from parts, and installed/configured everything on my own. My opinion is that mythtv and ubuntu (mythbuntu) has come a long way as a platform for end users, but they still have a long way to go I'm afraid. My biggest annoyance is still the same it was 12 years ago unfortunately, and I think it's to some extent become even worse over time. Graphics and Sound drivers...
I personally have fairly new nvidia card which I want 3d graphics on, and all the hardware accelerations etc, in other words I'm stuck with the nvidia drivers. You would think it would be easy with the proprietary hardware drivers stuff in Ubuntu, but it's not. It's actually worse than some years ago when I last handled these setups, then all you had to do was compile and install drivers in the correct kernel modules directory. Now you have to fight with umpteenth other installers which crashes and overwrites eachothers and so forth, and then when you do an update, all of a sudden you overwrite your working drivers with nonworking versions and you're stuck trying to figure out just what happened. Also, the choice of good graphics cards has become smaller imho. If you want something powerful, you're stuck with nvidia or ati. Both drivers are completely horrible to get working. I'm hoping the rumours I've heard lately will turn true here, and we'll finally see better support for open source software from both companies, at least if they could make a single decent installer for the proprietary drivers in the common Linux distributions.
And my final gripe, which isn't so large as the other ones, the sound drivers. Sound was absolutely horrible back in the days with OSS, whatever soundcard I tried to install, I winded up with either having to run the trial OSS drivers, or choosing between no sound and buying the OSS drivers. This has become much better happily. It's still not working flawlessly as I just found out (SPDIF took a few hours to get working, and I still haven't gotten 5.1 output to work correctly over SPDIF).
These are critical areas of an OS (you expect sound and graphics to "work out of the box" these days, not having to screw around with settings/drivers/installers as soon as you deviate by a single micron from the specifications.
On top of this, I had some more serious issues with my iMON PAD remote, once again after reinstalling the system. That I can live with, but it's a serious annoyance. For some reason, the configurations shipped with mythbuntu had a bunch of codes that where off by a few numbers every here and there, and then there was a lot of buttons not connected between lirc to mplayer and mythtv.
Apart from this, I'm very happy with the setup by now. The basic functionality is there, but it's made for tweaking and having fun, so there's still a lot of things I'm interested in doing on it :-).
By now, I'm mainly waiting for work to start again, I feel rested, I've gotten to fiddle with some hardware and software, and I got new energy for the new year. I just need to try and get working on my webpage and stuff like that a little bit more so I can finally finish it. Like all IT projects, it's running very late ;-).
söndag 23 november 2008
Build components
After a weekend of work, I finally got myself a build component that I'm semi-pleased with, for C and C++ projects, using Subversion. Most likely works for any other lower level programming language as well.
First off, structure. Each component is it's own BTT(Branches, Tags, Trunk)-root, residing in a Project_Modules directory in subversion. Each component contains an inc, src, test and a stubs directory. Rationale for the BTT-root is that, with a separate BTT-root for each component we can raise the version of each separate component without having to raise it for the entire project.
The Project directory resides on the same level as Project_Modules, and is empty, only containing the subversion property externals pointing to the trunks of the Components in Project_Modules. Rationale for this is to have a simple place to checkout the entire project. It's a bit dangerous when working with branches, and requires a little bit extra care so one doesnt write into the trunk out of mistake. Possibly block everyone but a specific user to write in the trunks and have that CM person do all the branching/merging. It is time consuming however.
It looks something like this:
First off, structure. Each component is it's own BTT(Branches, Tags, Trunk)-root, residing in a Project_Modules directory in subversion. Each component contains an inc, src, test and a stubs directory. Rationale for the BTT-root is that, with a separate BTT-root for each component we can raise the version of each separate component without having to raise it for the entire project.
The Project directory resides on the same level as Project_Modules, and is empty, only containing the subversion property externals pointing to the trunks of the Components in Project_Modules. Rationale for this is to have a simple place to checkout the entire project. It's a bit dangerous when working with branches, and requires a little bit extra care so one doesnt write into the trunk out of mistake. Possibly block everyone but a specific user to write in the trunks and have that CM person do all the branching/merging. It is time consuming however.
It looks something like this:
- Project_Modules
- Component1
- inc
- src
- test
- stubs
- Component2
- inc
- src
- test
- stubs
- Project
lördag 22 november 2008
Criminalized generation
So, IPRED is coming to this country, Swedens government is forcing it into effect. Even though there has been quite heavy resistance and a lot of people don't like it. I agree. It's a complete nutjob of a law. Before moving on, let me state that I am here discussing the Swedish implementation of the law. This is even further going than the original EU directive COM(2006)0168. The best part is, they just "softened it". Ie, it was even worse from the beginning.
As has already been said by thousands of others, but it can't be said enough times. The law moves the burden of the police work from the (almost) objective police to the absolutely partial owners themself. Let's consider this: We have for centuries had a police force because they are objective. They deal with criminals and they should hopefully not take sides for either part in a case, it's left to the court to do this.
With IPRED, the entire burden of investigating a crime is moved to the plaintiff. The plaintiff (in this case, the intellectual property owner) or someone working for the plaintiff, finds someone downloading a piece that they "own". They then move on to demanding the name and contact information of that person from the Internet Service Provider (ISP) of the Internet address of that specific downloader. Current law does not tell the ISP that it has to comply with the demand. IPRED does. The plaintiff can now move on to the next step below.
The plaintiff are then free to send monetary demands to the "defender", who will find out about the problem with the monetary demand. The monetary demand is formed as "pay us money or we draw you in front of a court and you will loose a lot more". Basically, you will have a gigantic mass of people just paying out of freight "who knows, maybe my kids/spouse/visitor did download that song on my computer?". Or how about framing someone you don't like, it's not gonna be hard, trust me. Don't like your neighbour, go download a free program and hack him, then set up a bittorrent client to keep downloading/uploading from their computer.
Now, this is the basic argument people have against this new law. Unfortunately, it has been cobbled together by retards and rather IQ-free people and been compromised by to such a degree that it's no longer coherent. One of the sideeffects of this law is that it will become illegal to buy an application or download a open source application and then run on your own computer. The same plaintiff above could sue every single owner of a Microsoft Windows Vista license (for example) if they can find a instance where Vista steps on their patent.
This comes to mind, when one reads IPRED:
When the Nazis came for the communists,
I remained silent;
I was not a communist.
When they locked up the social democrats,
I remained silent;
I was not a social democrat.
When they came for the trade unionists,
I did not speak out;
I was not a trade unionist.
When they came for the Jews,
I remained silent;
I was not a Jew.
When they came for me,
there was no one left to speak out.
As has already been said by thousands of others, but it can't be said enough times. The law moves the burden of the police work from the (almost) objective police to the absolutely partial owners themself. Let's consider this: We have for centuries had a police force because they are objective. They deal with criminals and they should hopefully not take sides for either part in a case, it's left to the court to do this.
With IPRED, the entire burden of investigating a crime is moved to the plaintiff. The plaintiff (in this case, the intellectual property owner) or someone working for the plaintiff, finds someone downloading a piece that they "own". They then move on to demanding the name and contact information of that person from the Internet Service Provider (ISP) of the Internet address of that specific downloader. Current law does not tell the ISP that it has to comply with the demand. IPRED does. The plaintiff can now move on to the next step below.
The plaintiff are then free to send monetary demands to the "defender", who will find out about the problem with the monetary demand. The monetary demand is formed as "pay us money or we draw you in front of a court and you will loose a lot more". Basically, you will have a gigantic mass of people just paying out of freight "who knows, maybe my kids/spouse/visitor did download that song on my computer?". Or how about framing someone you don't like, it's not gonna be hard, trust me. Don't like your neighbour, go download a free program and hack him, then set up a bittorrent client to keep downloading/uploading from their computer.
Now, this is the basic argument people have against this new law. Unfortunately, it has been cobbled together by retards and rather IQ-free people and been compromised by to such a degree that it's no longer coherent. One of the sideeffects of this law is that it will become illegal to buy an application or download a open source application and then run on your own computer. The same plaintiff above could sue every single owner of a Microsoft Windows Vista license (for example) if they can find a instance where Vista steps on their patent.
This comes to mind, when one reads IPRED:
When the Nazis came for the communists,
I remained silent;
I was not a communist.
When they locked up the social democrats,
I remained silent;
I was not a social democrat.
When they came for the trade unionists,
I did not speak out;
I was not a trade unionist.
When they came for the Jews,
I remained silent;
I was not a Jew.
When they came for me,
there was no one left to speak out.
Prenumerera på:
Inlägg (Atom)
