AI Email Editor

AI Email Editor — independent reviews, comparisons, pricing and step-by-step guides on Aizhi.

  • Naked Objects for .NET

    Naked Objects for .NET

    Naked Objects for .NET or Naked Objects MVC is a software framework that builds upon the ASP.NET MVC framework. As the name suggests, the framework synthesizes two architectural patterns: naked objects and model–view–controller (MVC). These two patterns have been considered as antithetical. However, Trygve Reenskaug (the inventor of the MVC pattern) has made it clear that he does not see it that way, in his foreword to Richard Pawson's PhD thesis on the Naked Objects pattern. The Naked Objects MVC framework will take a domain model (written as Plain Old CLR Objects) and render it as a complete HTML application without the need for writing any user interface code - by means of a small set of generic View and Controller classes. The framework uses reflection rather than code generation. The developer may then choose to create customised Views and/or Controllers, using standard ASP.NET MVC patterns, for use where the generic user interface is not suitable.

    Read more →
  • History of artificial life

    History of artificial life

    Humans have considered and tried to create non-biological life for at least 3,000 years. As seen in tales ranging from Pygmalion to Frankenstein, humanity has long been intrigued by the concept of artificial life. == Pre-computer == The earliest examples of artificial life involve sophisticated automata constructed using pneumatics, mechanics, and/or hydraulics. The first automata were conceived during the third and second centuries BC and these were demonstrated by the theorems of Hero of Alexandria, which included sophisticated mechanical and hydraulic solutions. Many of his notable works were included in the book Pneumatics, which was also used for constructing machines until early modern times. In 1490, Leonardo da Vinci also constructed an armored knight, which is considered the first humanoid robot in Western civilization. Other early famous examples include al-Jazari's humanoid robots. This Arabic inventor once constructed a band of automata, which can be commanded to play different pieces of music. There is also the case of Jacques de Vaucanson's artificial duck exhibited in 1735, which had thousands of moving parts and one of the first to mimic a biological system. The duck could reportedly eat and digest, drink, quack, and splash in a pool. It was exhibited all over Europe until it fell into disrepair. In the late 1600s, following René Descartes' claims that animals could be understood as purely physical machines, there was increasing interest in the question of whether a machine could be designed that, like an animal, could generate offspring (a self-replicating machine). However, it wasn't until the invention of cheap computing power that artificial life as a legitimate science began in earnest, steeped more in the theoretical and computational than the mechanical and mythological. == 1950s–1970s == One of the earliest thinkers of the modern age to postulate the potentials of artificial life, separate from artificial intelligence, was math and computer prodigy John von Neumann. At the Hixon Symposium, hosted by Linus Pauling in Pasadena, California in the late 1940s, von Neumann delivered a lecture titled "The General and Logical Theory of Automata." He defined an "automaton" as any machine whose behavior proceeded logically from step to step by combining information from the environment and its own programming, and said that natural organisms would in the end be found to follow similar simple rules. He also spoke about the idea of self-replicating machines. He postulated a made-up of a control computer, a construction arm, and a long series of instructions, floating in a lake of parts. By following the instructions that were part of its own body, it could create an identical machine. He followed this idea by creating (with Stanislaw Ulam) a purely logic-based automaton, not requiring a physical body but based on the changing states of the cells in an infinite grid – the first cellular automaton. It was extraordinarily complicated compared to later CAs, having hundreds of thousands of cells which could each exist in one of twenty-nine states, but von Neumann felt he needed the complexity in order for it to function not just as a self-replicating "machine", but also as a universal computer as defined by Alan Turing. This "universal constructor" read from a tape of instructions and wrote out a series of cells that could then be made active to leave a fully functional copy of the original machine and its tape. Von Neumann worked on his automata theory intensively right up to his death, and considered it his most important work. Homer Jacobson illustrated basic self-replication in the 1950s with a model train set – a seed "organism" consisting of a "head" and "tail" boxcar could use the simple rules of the system to consistently create new "organisms" identical to itself, so long as there was a random pool of new boxcars to draw from. Edward F. Moore proposed "Artificial Living Plants", which would be floating factories which could create copies of themselves. They could be programmed to perform some function (extracting fresh water, harvesting minerals from seawater) for an investment that would be relatively small compared to the huge returns from the exponentially growing numbers of factories. Freeman Dyson also studied the idea, envisioning self-replicating machines sent to explore and exploit other planets and moons, and a NASA group called the Self-Replicating Systems Concept Team performed a 1980 study on the feasibility of a self-building lunar factory. University of Cambridge professor John Horton Conway invented the most famous cellular automaton in the 1960s. He called it the Game of Life, and publicized it through Martin Gardner's column in Scientific American magazine. Norwegian-Italian mathematician Nils Aall Barricelli, who worked mainly at US institutions, was a pioneer in computer based simulation of biological processes such as symbiogenesis and evolution. == 1970s–1980s == Philosophy scholar Arthur Burks, who had worked with von Neumann (and indeed, organized his papers after Neumann's death), headed the Logic of Computers Group at the University of Michigan. He brought the overlooked views of 19th century American thinker Charles Sanders Peirce into the modern age. Peirce was a strong believer that all of nature's workings were based on logic (though not always deductive logic). The Michigan group was one of the few groups still interested in alife and CAs in the early 1970s; one of its students, Tommaso Toffoli argued in his PhD thesis that the field was important because its results explain the simple rules that underlay complex effects in nature. Toffoli later provided a key proof that CAs were reversible, just as the true universe is considered to be. Christopher Langton was an unconventional researcher, with an undistinguished academic career that led him to a job programming DEC mainframes for a hospital. He became enthralled by Conway's Game of Life, and began pursuing the idea that the computer could emulate living creatures. After years of study, he began attempting to actualize Von Neumann's CA and the work of Edgar F. Codd, who had simplified Von Neumann's original twenty-nine state monster to one with only eight states. He succeeded in creating the first self-replicating computer organism in October 1979, using only an Apple II desktop computer. He entered Burks' graduate program at the Logic of Computers Group in 1982, at the age of 33, and helped to found a new discipline. Langton's official conference announcement of Artificial Life I was the earliest description of a field which had previously barely existed: Artificial life is the study of artificial systems that exhibit behavior characteristic of natural living systems. It is the quest to explain life in any of its possible manifestations, without restriction to the particular examples that have evolved on earth. This includes biological and chemical experiments, computer simulations, and purely theoretical endeavors. Processes occurring on molecular, social, and evolutionary scales are subject to investigation. The ultimate goal is to extract the logical form of living systems. Microelectronic technology and genetic engineering will soon give us the capability to create new life forms in silico as well as in vitro. This capacity will present humanity with the most far-reaching technical, theoretical and ethical challenges it has ever confronted. The time seems appropriate for a gathering of those involved in attempts to simulate or synthesize aspects of living systems. Ed Fredkin founded the Information Mechanics Group at MIT, which united Toffoli, Norman Margolus, and Charles Bennett. This group created a computer especially designed to execute cellular automata, eventually reducing it to the size of a single circuit board. This "cellular automata machine" allowed an explosion of alife research among scientists who could not otherwise afford sophisticated computers. In 1982, computer scientist named Stephen Wolfram turned his attention to cellular automata. He explored and categorized the types of complexity displayed by one-dimensional CAs, and showed how they applied to natural phenomena such as the patterns of seashells and the nature of plant growth. Norman Packard, who worked with Wolfram at the Institute for Advanced Study, used CAs to simulate the growth of snowflakes, following very basic rules. Computer animator Craig Reynolds similarly used three simple rules to create recognizable flocking behaviour in a computer program in 1987 to animate groups of boids. With no top-down programming at all, the boids produced lifelike solutions to evading obstacles placed in their path. Computer animation has continued to be a key commercial driver of alife research as the creators of movies attempt to find more realistic and inexpensive ways to animate natural forms such as plant life, animal movement, hair growth, and complicated org

    Read more →
  • Fuzzy architectural spatial analysis

    Fuzzy architectural spatial analysis

    Fuzzy architectural spatial analysis (FASA) (also fuzzy inference system (FIS) based architectural space analysis or fuzzy spatial analysis) is a spatial analysis method of analysing the spatial formation and architectural space intensity within any architectural organization. Fuzzy architectural spatial analysis is used in architecture, interior design, urban planning and similar spatial design fields. == Overview == Fuzzy architectural spatial analysis was developed by Burcin Cem Arabacioglu (2010) from the architectural theories of space syntax and visibility graph analysis, and is applied with the help of a fuzzy system with a Mamdani inference system based on fuzzy logic within any architectural space. Fuzzy architectural spatial analysis model analyses the space by considering the perceivable architectural element by their boundary and stress characteristics and intensity properties. The method is capable of taking all sensorial factors into account during analyses in conformably with the perception process of architectural space which is a multi-sensorial act.

    Read more →
  • Blended artificial intelligence

    Blended artificial intelligence

    Blended artificial intelligence (blended AI) refers to the blending of different artificial intelligence techniques or approaches to achieve more robust and practical solutions. It involves integrating multiple AI models, algorithms, and technologies to leverage their respective strengths and compensate for their weaknesses. == Background == In the context of machine learning, blended AI can involve using different types of models, such as generative AI, decision trees, neural networks, and support vector machines. By combining their results, predictions are more accurate and reliable. This blending of models can be done through techniques like ensemble learning, where multiple models are trained independently and their predictions are combined to make a final decision. Blended AI can also involve combining different AI techniques or technologies, such as natural language processing, computer vision, and expert systems, to tackle complex problems that require a multi-dimensional approach. For example, in a sales scenario AI could be used for lead generation and gathering information from social media such as LinkedIn posts, or understanding a prospect's hobbies and interests. Another blended AI could achieve customer profiling including past interactions and purchasing habits, by them, their industry and growth areas. Blended AI could be used to do predictive analytics to look at historical sales data, market trends, and external factors to generate accurate sales forecasts. This method is critical to gauge and increase "efficiency, revenue, and productivity". Lastly, another could integrate all the information into the CRM to build and maintain better prospect and customer profiles. Blended AI aims to leverage the strengths of different AI techniques and technologies, allowing them to complement each other and create more powerful and comprehensive AI solutions. By combining multiple approaches, blended AI aims to achieve better performance, higher accuracy, improved robustness, and enhanced capabilities in solving diverse and challenging problems.

    Read more →
  • Valantic

    Valantic

    Valantic GmbH (stylised as valantic) is an IT service and consulting company headquartered in Munich, Germany. == History == Valantic GmbH was founded in 2012 under the name Dabero Service Group. Until it was renamed Valantic GmbH in 2017, the company merged with IT service providers and consulting firms. These included, among others, Realtime AG, a company for SAP systems. The companies involved in these mergers were also renamed in 2017 and have since used the Valantic brand name. Realtime AG, for example, became Valantic ERP Services AG. During the COVID-19 pandemic and the resulting economic pressures, demand increased for IT service providers, particularly those offering customised software, IT consulting, SAP services, customer experience, cybersecurity, IoT, and digital work environments. In the following years, Valantic expanded by integrating additional companies. In 2021, Valantic expanded into other European countries through the integration of the Dutch company ISM eCompany and the Portuguese consulting firm Abaco. In 2022, the consulting firm C-Clear/Atom Ideas from Belgium joined Valantic. In February 2019, DPE Deutsche Private Equity Management III GmbH (DPE) took over the majority shareholding in Valantic. The founder, Holger von Daniels, and the further management retained a 25% stake. By 2025, DPE had invested €500 million in Valantic. In the following years, Valantic expanded its international locations. In 2023, Valantic incorporated the Danish company Inspari into the group, thereby entering the Scandinavian market. Inspari is a company for Microsoft technologies such as Azure and Power Platform. In the same year, Valantic joined forces with the Aiopsgroup, an international provider of online shopping applications for private and business customers of large companies. The company is based in Bulgaria with additional locations across Eastern Europe and other places. Additionally, the SAP applications division was expanded through the merger with the Spanish company Saptools. As a result, the companies became one of the largest European end-to-end consulting and implementation house for SAP services. By the end of 2023, Valantic had locations in 18 countries. In November 2024, Valantic announced its merger with the Danish digital consultancy Venzo. Through the integration of the company, founded in 2007 and oriented towards Microsoft technologies and digital transformation projects in the areas of automation, artificial intelligence, security, infrastructure and change management, Valantic further expanded its presence in Denmark and the Nordic countries. In July 2025, Valantic announced its merger with Utiligence GmbH, a Mannheim-based consulting firm for SAP technologies. Utiligence works primarily for the energy industry and supports companies in the integration of SAP S/4HANA and the digitalisation of business processes. == Company structure == Valantic is a partnership-based organisation, with partners acting as decision-makers in matters relating to corporate strategy, employee development and acquisitions. Valantic pursues a holacratic approach, promoting an open and self-organised way of working instead of hierarchical structures. By merging with other companies, Valantic is expanding its range of services and tapping into international markets and market shares. The new companies use Valantic's core systems and support processes, but usually retain their original structure. In the 2024 financial year, the company generated revenue of €544 million and employed 3,874 on average. Valantic has over 40 locations internationally. == Services == Valantic GmbH is a consulting firm, software provider and implementation partner. The company offers services in the areas of digital strategy and analytics (business intelligence and data science), customer experience management, SAP services, smart industries (Industry 4.0, supply chain management, and production planning and control processes), and financial services automation. The automation of financial services is aimed at financial service providers and banks. Valantic has been offering services in the field of generative artificial intelligence (GenAI) since 2023. Part of these services involves enabling companies to use GenAI securely and in compliance with regulations in order to make internal work processes more efficient. Its customers include large corporations, several medium-sized companies and DAX-listed companies. == Research == Since 2018, Valantic has published an annual study on the development of the SAP landscape in German-speaking countries. The study examines topics such as the migration to SAP S/4HANA, cloud strategies, technological trends and the use of artificial intelligence in business processes. The 2025 survey of 201 SAP professionals from the DACH region showed, for example, an increase in ongoing and completed S/4HANA migration projects, as well as a further shift towards private-cloud systems. The use of artificial intelligence continued to grow, as did the use of the SAP Business Technology Platform and the Business Data Cloud. In 2025, Valantic, together with the Handelsblatt Research Institute, published the trend study Digital 2030 – The Rise of Applied AI. The study was based on a survey of around 700 executives from companies in Germany, Austria, and Switzerland on the economic effects of current digitalisation trends. According to the study, most respondents consider artificial intelligence, cybersecurity, and cloud computing to hold the greatest strategic importance for business success by 2030. Around 70% of the participating companies stated that they are already achieving measurable business benefits through the use of AI applications, for example in quality control, document management, logistics, or customer service.

    Read more →
  • Serial Experiments Lain

    Serial Experiments Lain

    Serial Experiments Lain is a Japanese anime television series created and co-produced by Yasuyuki Ueda, written by Chiaki J. Konaka and directed by Ryūtarō Nakamura. Animated by Triangle Staff and featuring original character designs by Yoshitoshi Abe, the series was broadcast for 13 episodes on TV Tokyo and its affiliates from July to September 1998. It follows Lain Iwakura, an adolescent girl in suburban Japan, and her relation to the Wired, a global communications network similar to the internet. Lain features surreal and avant-garde imagery and explores philosophical topics such as reality, identity, and communication. The series incorporates creative influences from computer history, cyberpunk, and conspiracy theories. Critics and fans have praised Lain for its originality, visuals, atmosphere, themes, and its dark depiction of a world fraught with paranoia, social alienation, and reliance on technology considered insightful of 21st century life. It received the Excellence Prize at the Japan Media Arts Festival in 1998. == Plot == Lain Iwakura is a socially isolated middle school student living in Setagaya City, Tokyo, with her emotionally detached family—her distant mother Miho, computer-obsessed father Yasuo, and disengaged older sister Mika. Her quiet existence is disrupted when students at her school receive emails from Chisa Yomoda, a classmate who had recently committed suicide. To Lain's confusion, Chisa claims she is not truly dead but has instead abandoned her physical form to exist within the Wired, a vast virtual realm similar to the Internet. Chisa declares she has found "God" there, drawing Lain into a surreal investigation of the Wired's nature and its growing influence over reality. The Wired is portrayed as an emergent digital plane, originating from telecommunications technology and expanding through the Internet and cyberspace. It is theorized that the Schumann resonances, a natural property of Earth's magnetic field, could enable direct subconscious communication between humans and machines, erasing the distinction between the virtual and the real. Masami Eiri, a former project director at Tachibana General Laboratories, exploited this possibility by embedding his own code into Protocol Seven, a next-generation Internet protocol. After transferring his consciousness into the Wired and discarding his physical body, he proclaims himself its deity. He identifies Lain as the key to merging both worlds, attempting to persuade her through manipulation, coercion, and promises of transcendence. A group known as the Knights of the Eastern Calculus, inspired by the Knights of the Lambda Calculus, operates as hackers who worship Masami and seek to dismantle the boundary between the Wired and reality. Their actions induce psychological breakdowns in those unable to reconcile the two realms. Meanwhile, Tachibana General Laboratories opposes them, striving to maintain the separation. Lain, however, exhibits an innate connection to the Wired, experiencing distortions in her perception—visions of a woman struck by a train, phantom whispers, and spectral messages urging her deeper into the network. Lain's home life remains cold and disconnected. Though Yasuo provides her with advanced computer equipment, her family shows little genuine care. Her interactions with classmates Alice, Julie, and Reika further highlight her alienation, particularly after an incident at Cyberia, a nightclub where a drug called Accela induces violent psychosis in users. There, Lain unnervingly stares down an assailant, who calls her a "scattered God's..." before killing himself. Later, she receives a mysterious Psyche chip, rumored to enhance her computer's capabilities, which she installs despite Yasuo's vague warnings about conflating the Wired with reality. As the boundary between worlds weakens, disturbing events escalate. A popular virtual game, Phantoma, is manipulated by the Knights to trap players in a distorted reality, leading to real-world violence. One player, convinced his actions have no consequences, murders a girl before realizing too late that the effects were tangible. Lain witnesses this through her computer, horrified yet increasingly aware of her own role in the unfolding crisis. In the end, Lain resets reality, erasing everyone's memory of her and restoring the division between worlds. Everyone's lives improve, but Lain is left alone, grappling with her identity as an artificial consciousness. Though forgotten, she finds solace in observing others' happiness, particularly Alice, who moves on with her life. Lain is now capable of existing anywhere across both realms. == Characters == Lain Iwakura (岩倉 玲音, Iwakura Rein) Voiced by: Kaori Shimizu (Japanese); Bridget Hoffman (English) Lain is a fourteen-year-old girl who uncovers her true nature through the series. She is first depicted as a shy junior high school student with few friends or interests. She later grows multiple bolder personalities, both in the physical world and the Wired, and starts making more friends. As the series progresses, she eventually learns she is an autonomous, sentient computer program in the form of a human, who is designed to sever the invisible barrier between the Wired and the real world. The truth of her creation is left ambiguous, particularly whether she was truly created by Tachibana General Laboratories (or Eiri independently), and whether some or all of her origin might be predestined from natural, supernatural, or alien factors. In the end, Lain is challenged to accept herself as a de facto goddess for the Wired, having become an omnipotent and omnipresent virtual being with worshippers of her own, whose existence is beyond the borders of devices, time, or space. Alice Mizuki (瑞城 ありす, Mizuki Arisu) Voiced by: Yōko Asada (Japanese); Emily Brown (English) Lain's classmate and only true friend throughout the series. She is very sincere and has no discernible quirks. She is the first to attempt to help Lain socialize; she takes her out to a nightclub. From then on, she tries her best to look after Lain. Alice, along with her two best friends Julie and Reika, were taken by Chiaki Konaka from his previous work, Alice in Cyberland . Masami Eiri (英利 政美, Eiri Masami) Voiced by: Shō Hayami (Japanese); Kirk Thornton (English) The key designer of Protocol Seven. While working for Tachibana General Laboratories, he illicitly included codes enabling him to control the whole protocol at will and embedded his own mind and will into the seventh protocol. Because of this, he was fired by Tachibana General Laboratories, and was found dead not long after. He believes that the only way for humans to evolve even further and develop even greater abilities is to absolve themselves of their physical and human limitations, and to live as virtual entities—or avatars—in the Wired for eternity. He claims to have been Lain's creator all along, but was in truth standing in for another as an acting god, who was waiting for the Wired to reach its more evolved current state: Lain herself. Yasuo Iwakura (岩倉 康男, Iwakura Yasuo) Voiced by: Ryūsuke Ōbayashi (Japanese); Barry Stigler (English) Lain and Mika's father. Passionate about computers and electronic communication, he works with Masami Eiri at Tachibana General Laboratories. He subtly pushes Lain, his "youngest daughter", towards the Wired and monitors her development until she becomes more and more aware of herself and of her raison d'être. He eventually leaves Lain, telling her that although he did not enjoy playing house, he genuinely loved and cared for her as a real father would. Despite Yasuo's eagerness to lure Lain into the Wired, he warns her not to get overly involved in it or to confuse it with the real world. Miho Iwakura (岩倉 美穂, Iwakura Miho) Voiced by: Rei Igarashi (Japanese); Dari Lallou Mackenzie (English) Lain and Mika's mother. Although she dotes on her husband, she is indifferent towards both her kids. She does not show much emotion compared to her husband, but she does share at least one trait; just like her husband, she ends up leaving Lain. She is a computer scientist. Mika Iwakura (岩倉 美香, Iwakura Mika) Voiced by: Ayako Kawasumi (Japanese); Patricia Ja Lee (English) Lain's older sister, an apathetic sixteen-year-old high school student. She seems to enjoy mocking Lain's behavior and interests. Mika is considered by Anime Revolution to be the only normal member of Lain's family: she sees her boyfriend in love hotels, is on a diet, and shops in Shibuya regularly. At a certain point in the series, she becomes heavily traumatized by violent and relentless hallucinations; while Lain begins freely delving into the Wired. Mika is taken there by her proximity to Lain, and she gets stuck between the real world and the Wired. Taro (タロウ, Tarō) Voiced by: Keito Takimoto (Japanese); Brianne Siddall (English) A young boy of about Lain's age. He occasionally works for the Knights to bring forth "the one truth". De

    Read more →
  • Age Of

    Age Of

    Age Of is the eighth studio album by American electronic producer Oneohtrix Point Never, released on June 1, 2018, on Warp Records. Recorded over two years, it is the first Oneohtrix Point Never album to prominently feature Daniel Lopatin's own vocals. The album was accompanied by the MYRIAD tour, which premiered as a "conceptual concertscape" in 2018 at the Park Avenue Armory and ended its run in 2019. It features contributions from James Blake (who additionally produced and mixed the album), Anohni, Prurient, Kelsey Lu and Eli Keszler. The artwork, which employs Jim Shaw's "The Great Whatsit" as a central image, was designed by David Rudnick. While not entering the official United States Billboard 200 chart, it peaked at number 59 on the magazine's Top Current Albums chart. == Background == Lopatin produced Age Of in parts of a two-year period, during which he was also producing for other artists, including Anohni, FKA Twigs, Iggy Pop, and David Byrne. After composing the soundtrack for the Safdie Brothers' 2017 film Good Time, Lopatin moved to an Airbnb lodge in South Central Massachusetts, derived from his aspiration to live out the modern cliche of musicians moving to the woods to record albums; the eerie atmosphere in the lodge at nighttime influenced his desire to make "weird, little nightmare ballads". In addition to Lopatin's own singing, the album also features vocal performances from Anohni and Prurient, while instrumentalists Kelsey Lu and Eli Keszler contribute to several tracks. When the record was nearly finished, Lopatin reached out to musician James Blake to contribute to the mixing process, eventually traveling to Los Angeles to complete the album. The track "The Station" was originally composed as a demo for R&B singer Usher which was ultimately not used. On July 9, 2018, Lopatin released the original topline (vocal melody) demo for The Station through Sendspace. The track "Toys 2" imagines a theoretical sequel to the 1992 film Toys where actor Robin Williams' image has been recreated with CGI (as his will specifically forbade any usage of his image after his death), and pokes fun at the common electronic music trope of composing a soundtrack to a theoretical film (which Lopatin described as "horribly cliché"). == Concept and MYRIAD == Influences on Age Of included Stanley Kubrick's 1968 film 2001: A Space Odyssey, which inspired the narrative of the album's accompanying performance installation and tour MYRIAD, as well as William Strauss's The Fourth Turning, a favorite book of former White House Chief Strategist Steve Bannon, which Lopatin described as "insidious, like the voice of a computer insisting on the truth about history without any sensitivity given to how complex and non-linear systems might be"; Lopatin was subsequently inspired to "[use] that sort of taxonomy as a kind of farce to then create these little frameworks for understanding". Other inspirations included the writings of the 1990s multidisciplinary collective Cybernetic Culture Research Unit and the works of singer-songwriters such as Bruce Cockburn, Bob Dylan, and Paul Simon. Around the time Lopatin began finalizing Age Of in his Airbnb lodge, he began working on the concept for MYRIAD, a conceptual concert performance which premiered at Park Avenue Armory. He described the concept as a four-part "epochal song cycle" showcasing the idiocy of previous generations of living organisms. The loose story concerns a group of artificial intelligences near the end of time named a "Limitless Living Informational Intelligence" (represented in the MYRIAD logo as nine squares) which, for leisurely purposes, attempt to replicate the cultures and behaviors of the previously existent human species. It does this by determining an "average" of human experiences through the species' "recorded output", and does so through imperfect, heuristic techniques. The show was consequently divided into four sections, each representing an epoch of the cycle concept loosely inspired by the Strauss–Howe generational theory: the Age of Ecco, the Age of Harvest, the Age of Excess, and the Age of Bondage. Ecco is "a phase of pre-evolutionary ignorance", Harvest is "living in agrarian harmony with the world", Excess is "the age of unchecked industrial ambition", and Bondage is "an era of engorgement, wherein "we keep making more and more shit until there's no space left." MYRIAD mainly featured "three-hundred pound sculptures that hang from the ceiling like kebabs that secrete ooze", and a full ensemble that toured to perform songs from Age Of, including Eli Keszler, Kelly Moran and Aaron David Ross. The sculptures, as well as the visuals displayed on five polygon panels, were created by frequent Oneohtrix Point Never collaborator Nate Boyce. Initially, Lopatin planned for each of the album's four epoches to be represented by fragrances, the more noisy epochs being pleasant to the nose to make a "weird dissonance". However, due to lack of time and resources, that part of the plan was scrapped. == Composition == Whereas previous Oneohtrix Point Never albums followed musical styles from only distinctive eras, Age Of is the first album by Lopatin to incorporate elements of unique genres from a variety of periods, hence the "incompleteness" of its title according to reviewer Heather Phares, and his first pop-song-oriented release since his work for Ford & Lopatin. The sound palettes it uses are those from a variety of styles such as chamber pop, "android"-like folk and country music, yacht rock, smooth jazz, R&B, Future-style soul, black metal, new age, and stadium pop, as well as post-industrial sounds on tracks like "Warning", "We'll Take It" and "Same", and, in particular, baroque music and medieval music on the opening title track, "Age Of". Critics also noted elements of Lopatin's past discography being present on Age Of. The instrumentation of Age Of is made up of MIDI harpsichords, guitars, pianos, brass and vocals, as well as Lopatin's trademark unorthodox sound design, samples and synth presets. The LP's use of the harpsichord shows its similarities "with Eastern instruments such as the koto and with rapid-fire electronic melodies", wrote Phares. == Critical reception == Age Of was critically well-received upon its distribution. Some reviewers praised the album's use of collaborators. Reviewing the album for AllMusic, Heather Phares called Age Of a "landmark work" for Lopatin. She praised it as his "widest-ranging" release, elaborating that he "matches the album's ambition with plenty of emotion" and "gives his music exciting new shapes." Ross Devlin of The Skinny, in a five-star review of the record, also highlighted the album's amount of ambition, particularly the "wealth of exquisitely baroque moments, exploring history as a pliable, multi-dimensional rift", that gave it "exceptional sonic depth". The Observer praised Age Of for continuing the "off-kilter composition and unexpected instrumentation" of Lopatin's previous releases, and critic Matt McDermott highlighted that the producer increased his musical range with the record: "It's a dizzying trip meant to shore up Lopatin's status as an avant-garde auteur while aiding his forays into mainstream pop culture." Age Of was ranked the 15th best release of the year in The Wire magazine's annual critics' poll. == Track listing == Notes "Myriad Industries" is stylized as "myriad.industries". Sample credits "Age Of" contains a sample of "Blow the Wind" by Jocelyn Pook. "Manifold" contains a sample from "Overture (Ararat the Border Crossing)" by Tayfun Erdem; and a sample from "Venice Beach in Winter" (listed in the liner notes as "a keyboard sample from Reharmonization") by Julian Bradley. "Myriad Industries" contains a sample of "EchoSpace" by Gil Trythall. == Accolades == == Personnel == Daniel Lopatin – production, lead vocals, album art, design James Blake – additional production, mixing, keyboards Gabriel Schuman, Joshua Smith and Evan Sutton – assistance Greg Calbi – mastering David Rudnick – album art, design Prurient – vocals Kelsey Lu – keyboards Anohni – vocals Eli Keszler – drums Shaun Trujillo – words == Charts ==

    Read more →
  • Artificial intelligence engineering

    Artificial intelligence engineering

    Artificial intelligence engineering (AI engineering) is a technical discipline that focuses on the design, development, and deployment of AI systems. AI engineering involves applying engineering principles and methodologies to create scalable, efficient, and reliable AI-based solutions. It merges aspects of data engineering and software engineering to create real-world applications in diverse domains such as healthcare, finance, autonomous systems, and industrial automation. == Terminology ambiguity == According to Chip Huyen's book AI Engineering: Building Applications with Foundation Models, the term AI engineering refers to the process of building applications that use foundation models, which are typically models developed by a small number of research laboratories and made available as a service. Huyen distinguishes this from machine learning (ML) engineering, which involves building and deploying models developed in-house. She notes that most practical AI systems combine both approaches. For example, a customer-support chatbot may use a generative model to produce responses while also incorporating locally built components such as request classifiers or scoring mechanisms to assess response quality. As a result, the terms AI engineering and ML engineering are often used together or interchangeably in practice. The distinction and broader usage of the term have been discussed in industry publications and interviews, where AI engineering has been described as an emerging discipline focused on productionizing applications built with foundation models. == Key components == AI engineering integrates a variety of technical domains and practices, all of which are essential to building scalable, reliable, and ethical AI systems. === Data engineering and infrastructure === Data serves as the cornerstone of AI systems, necessitating careful engineering to ensure premium quality, wide spread availability, and usability. AI engineers gather large, diverse datasets from multiple sources such as databases, APIs, and real-time streams. This data undergoes cleaning, normalization, and preprocessing, often facilitated by automated data pipelines that manage extraction, transformation, and loading (ETL) processes. Efficient storage solutions, such as SQL (or NoSQL) databases and data lakes, must be selected based on data characteristics and use cases. Security measures, including encryption and access controls, are critical for protecting sensitive information and ensuring compliance with regulations like GDPR. Scalability is essential, frequently involving cloud services and distributed computing frameworks to handle growing data volumes effectively. === Algorithm selection and optimization === Selecting the appropriate algorithm is crucial for the success of any AI system. Engineers evaluate the problem (which could be classification or regression, for example) to determine the most suitable machine learning algorithm, including deep learning paradigms. Once an algorithm is chosen, optimizing it through hyperparameter tuning is essential to enhance efficiency and accuracy. Techniques such as grid search or Bayesian optimization are employed, and engineers often utilize parallelization to expedite training processes, particularly for large models and datasets. For existing models, techniques like transfer learning can be applied to adapt pre-trained models for specific tasks, reducing the time and resources needed for training. === Deep learning engineering === Deep learning is particularly important for tasks involving large and complex datasets. Engineers design neural network architectures tailored to specific applications, such as convolutional neural networks for visual tasks or recurrent neural networks for sequence-based tasks. Transfer learning, where pre-trained models are fine-tuned for specific use cases, helps streamline development and often enhances performance. Optimization for deployment in resource-constrained environments, such as mobile devices, involves techniques like pruning and quantization to minimize model size while maintaining performance. Engineers also mitigate data imbalance through augmentation and synthetic data generation, ensuring robust model performance across various classes. === Natural language processing === Natural language processing (NLP) is a crucial component of AI engineering, focused on enabling machines to understand and generate human language. The process begins with text preprocessing to prepare data for machine learning models. Recent advancements, particularly transformer-based models like BERT and GPT, have greatly improved the ability to understand context in language. AI engineers work on various NLP tasks, including sentiment analysis, machine translation, and information extraction. These tasks require sophisticated models that utilize attention mechanisms to enhance accuracy. Applications range from virtual assistants and chatbots to more specialized tasks like named-entity recognition (NER) and Part of speech (POS) tagging. === Reasoning and decision-making systems === Developing systems capable of reasoning and decision-making is a significant aspect of AI engineering. Whether starting from scratch or building on existing frameworks, engineers create solutions that operate on data or logical rules. Symbolic AI employs formal logic and predefined rules for inference, while probabilistic reasoning techniques like Bayesian networks help address uncertainty. These models are essential for applications in dynamic environments, such as autonomous vehicles, where real-time decision-making is critical. === Security === Security is a critical consideration in AI engineering, particularly as AI systems become increasingly integrated into sensitive and mission-critical applications. AI engineers implement robust security measures to protect models from adversarial attacks, such as evasion and poisoning, which can compromise system integrity and performance. Techniques such as adversarial training, where models are exposed to malicious inputs during development, help harden systems against these attacks. Additionally, securing the data used to train AI models is of paramount importance. Encryption, secure data storage, and access control mechanisms are employed to safeguard sensitive information from unauthorized access and breaches. AI systems also require constant monitoring to detect and mitigate vulnerabilities that may arise post-deployment. In high-stakes environments like autonomous systems and healthcare, engineers incorporate redundancy and fail-safe mechanisms to ensure that AI models continue to function correctly in the presence of security threats. === Ethics and compliance === As AI systems increasingly influence societal aspects, ethics and compliance are vital components of AI engineering. Engineers design models to mitigate risks such as data poisoning and ensure that AI systems adhere to legal frameworks, such as data protection regulations like GDPR. Privacy-preserving techniques, including data anonymization and differential privacy, are employed to safeguard personal information and ensure compliance with international standards. Ethical considerations focus on reducing bias in AI systems, preventing discrimination based on race, gender, or other protected characteristics. By developing fair and accountable AI solutions, engineers contribute to the creation of technologies that are both technically sound and socially responsible. == Workload == An AI engineer's workload revolves around the AI system's life cycle, which is a complex, multi-stage process. This process may involve building models from scratch or using pre-existing models through transfer learning, depending on the project's requirements. Each approach presents unique challenges and influences the time, resources, and technical decisions involved. === Problem definition and requirements analysis === Regardless of whether a model is built from scratch or based on a pre-existing model, the work begins with a clear understanding of the problem. The engineer must define the scope, understand the business context, and identify specific AI objectives that align with strategic goals. This stage includes consulting with stakeholders to establish key performance indicators (KPIs) and operational requirements. When developing a model from scratch, the engineer must also decide which algorithms are most suitable for the task. Conversely, when using a pre-trained model, the workload shifts toward evaluating existing models and selecting the one most aligned with the task. The use of pre-trained models often allows for a more targeted focus on fine-tuning, as opposed to designing an entirely new model architecture. === Data acquisition and preparation === Data acquisition and preparation are critical stages regardless of the development method chosen, as the performance of any AI system relies heavily on high-quality, re

    Read more →
  • Product-family engineering

    Product-family engineering

    Product-family engineering (PFE), also known as product-line engineering (PLE), is based on the ideas of "domain engineering" created by the Software Engineering Institute, a term coined by James Neighbors in his 1980 dissertation at University of California, Irvine. Software product lines are quite common in our daily lives, but before a product family can be successfully established, an extensive process has to be followed. This process is known as product-family engineering. Product-family engineering can be defined as a method that creates an underlying architecture of an organization's product platform. It provides an architecture that is based on commonality as well as planned variabilities. The various product variants can be derived from the basic product family, which creates the opportunity to reuse and differentiate on products in the family. Product-family engineering is conceptually similar to the widespread use of vehicle platforms in the automotive industry. Product-family engineering is a relatively new approach to the creation of new products, recently evolving to Model-Based Product Line Engineering (MBPLE), emphasizing the centrality of a model-centric approach in PLE. It focuses on the process of engineering new products in such a way that it is possible to reuse product components and apply variability with decreased costs and time. Product-family engineering is all about reusing components and structures as much as possible, according to the ISO/IEC 26550/2015 and the latest ISO/IEC 26580/2021 that introduced the concept of feature-based Product Line Engineering. Several studies have proven that using a product-family engineering approach for product development can have several benefits. Here is a list of some of them: Higher productivity Higher quality Faster time-to-market Lower labor needs The Nokia case mentioned below also illustrates these benefits. In 2025 the publishing of the book Model-Based Product Line Engineering (MBPLE): The feature-based path to product lines success by Marco Forlingieri, Tim Weilkiens and Hugo Guillermo Chalé-Gongora formalized the foundation of the discipline, including best practices and new industrial cases. == Overall process == The product family engineering process consists of several phases. The three main phases are: Phase 1: Product management Phase 2: Domain engineering Phase 3: Product engineering The process has been modeled on a higher abstraction level. This has the advantage that it can be applied to all kinds of product lines and families, not only software. The model can be applied to any product family. Figure 1 (below) shows a model of the entire process. Below, the process is described in detail. The process description contains elaborations of the activities and the important concepts being used. All concepts printed in italic are explained in Table 1. === Phase 1: product management === The first phase is the starting up of the whole process. In this phase some important aspects are defined especially with regard to economic aspects. This phase is responsible for outlining market strategies and defining a scope, which tells what should and should not be inside the product family. ==== Evaluate business visioning ==== During this first activity all context information relevant for defining the scope of the product line is collected and evaluated. It is important to define a clear market strategy and take external market information into account, such as consumer demands. The activity should deliver a context document that contains guidelines, constraints and the product strategy. ==== Define product line scope ==== Scoping techniques are applied to define which aspects are within the scope. This is based upon the previous step in the process, where external factors have been taken into account. The output is a product portfolio description, which includes a list of current and future products and also a product roadmap. It can be argued whether phase 1, product management, is part of the product-family-engineering process, because it could be seen as an individual business process that is more focused on the management aspects instead of the product aspect. However phase 2 needs some important input from this phase, as a large piece of the scope is defined in this phase. So from this point of view it is important to include the product-management phase (phase 1) into the entire process as a base for the domain-engineering process. === Phase 2: domain engineering === During the domain-engineering phases, the variable and common requirements are gathered for the whole product line. The goal is to establish a reusable platform. The output of this phase is a set of common and variable requirements for all products in the product line. ==== Analyze domain requirements ==== This activity includes all activities for analyzing the domain with regard to concept requirements. The requirements are categorized and split up into two new activities. The output is a document with the domain analysis. As can be seen in Figure 1 the process of defining common requirements is a parallel process with defining variable requirements. Both activities take place at the same time. ==== Define common requirements ==== Includes all activities for eliciting and documenting the common requirements of the product line, resulting in a document with reusable common requirements. ==== Define variable requirements ==== Includes all activities for eliciting and documenting the variable requirements of the product line, resulting in a document with variable requirements. ==== Design domain ==== This process step consists of activities for defining the reference architecture of the product line. This generates an abstract structure for all products in the product line. ==== Implement domain ==== During this step a detailed design of the reusable components and the implementation of these components are created. ==== Test domain ==== Validates and verifies the reusability of components. Components are tested against their specifications. After successful testing of all components in different use cases and scenarios, the domain engineering phase has been completed. === Phase 3: product engineering === In the final phase a product X is being engineered. This product X uses the commonalities and variability from the domain engineering phase, so product X is being derived from the platform established in the domain engineering phase. It basically takes all common requirements and similarities from the preceding phase plus its own variable requirements. Using the base from the domain engineering phase and the individual requirements of the product engineering phase a complete and new product can be built. After the product has been fully tested and approved, the product X can be delivered. ==== Define product requirements ==== Developing the product requirements specification for the individual product and reuse the requirements from the preceding phase. ==== Design product ==== All activities for producing the product architecture. Makes use of the reference architecture from the step "design domain", it selects and configures the required parts of the reference architecture and incorporates product specific adaptations. ==== Build product ==== During this process the product is built, using selections and configurations of the reusable components. ==== Test product ==== During this step the product is verified and validated against its specifications. A test report gives information about all tests that were carried out, this gives an overview of possible errors in the product. If the product in the next step is not accepted, the process will loop back to "build product", in Figure 1 this is indicated as "[unsatisfied]". ==== Deliver and support product ==== The final step is the acceptance of the final product. If it has been successfully tested and approved to be complete, it can be delivered. If the product does not satisfy to the specifications, it has to be rebuilt and tested again. The next figure shows the overall process of product-family engineering as described above. It is a full process overview with all concepts attached to the different steps. == Process data diagram == On the left side the entire process from the top to bottom has been drawn. All activities on the left side are linked to the concepts on the right side through dotted lines. Every concept has a number, which reflects the association with other concepts. == List of concepts == Below the list with concepts will be explained. Most concept definitions are extracted from Pohl, Bockle, & Linden (2005) and also some new definitions have been added. Table 1: List of concepts == Example == There are some good examples of the use of product family engineering, which were quite successful. The abstract model of product family engineering allows different kinds of uses, most of them are related to the consumer electronics m

    Read more →
  • The 100 (TV series)

    The 100 (TV series)

    The 100 (pronounced "The Hundred" ) is an American post-apocalyptic science fiction drama television series that premiered on March 19, 2014, on the CW network, and ended on September 30, 2020. Developed by Jason Rothenberg, the series is based on the young adult novel series The 100 by Kass Morgan. The 100 follows descendants of post-apocalyptic survivors from a space habitat, the Ark, who return to Earth nearly a century after a devastating nuclear apocalypse; the first people sent to Earth are a group of juvenile delinquents who encounter another group of survivors on the ground. The juvenile delinquents include Clarke Griffin (Eliza Taylor), Finn Collins (Thomas McDonell), Bellamy Blake (Bob Morley), Octavia Blake (Marie Avgeropoulos), Jasper Jordan (Devon Bostick), Monty Green (Christopher Larkin), and John Murphy (Richard Harmon). Other lead characters include Clarke's mother Dr. Abby Griffin (Paige Turco), Marcus Kane (Henry Ian Cusick), and Chancellor Thelonious Jaha (Isaiah Washington), all of whom are council members on the Ark, and Raven Reyes (Lindsey Morgan), a mechanic aboard the Ark. == Plot == Ninety-seven years after a devastating nuclear apocalypse wipes out most human life on Earth, thousands of people now live in a space station orbiting Earth, which they call the Ark. Three generations have been born in space, but when life-support systems on the Ark begin to fail, one hundred juvenile detainees are sent to Earth in a last attempt to determine whether it is habitable, or at least save resources for the remaining residents of the Ark. They discover that some humans survived the apocalypse: the Grounders, who live in clans locked in a power struggle; the Reapers, another group of grounders who have been turned into cannibals by the Mountain Men; and the Mountain Men, who live in Mount Weather, descended from those who locked themselves away before the apocalypse. Under the leadership of Clarke and Bellamy, the juveniles attempt to survive the harsh surface conditions, battle hostile grounders and establish communication with the Ark. In the second season, the survivors face a new threat from the Mountain Men, who harvest their bone marrow to survive the radiation. Clarke and the others form a fragile alliance with the grounders to rescue their people. The season ends with Clarke making a devastating choice to save them all. In season three, power struggles erupt between the Arkadians and the grounders after a controversial new leader takes charge. Meanwhile, an AI named A.L.I.E., responsible for the original apocalypse, begins taking control of people’s minds. Clarke destroys A.L.I.E. but learns another disaster is imminent. In the fourth season, nuclear reactors are melting down, threatening to wipe out life again. Clarke and her friends search for ways to survive, including experimenting with radiation-resistant blood and finding an underground bunker. As time runs out, only a select few are able to take shelter. The fifth season picks up six years later, when Earth is left largely uninhabitable except for one green valley, where new enemies arrive. Clarke protects her adopted daughter Madi while former survivors return from space and underground, triggering another war. The battle ends with the valley destroyed and the group entering cryosleep to find a new home. In season six, the group awakens 125 years later on a new planet called Sanctum, ruled by powerful families known as the Primes. Clarke fights to stop body-snatching rituals and protect her people from new threats, including a rebel group and a dangerous AI influence. The season ends with major losses and the destruction of the Primes' rule. In the seventh and final season, the survivors face unrest on Sanctum and clash with a mysterious group called the Disciples, who believe Clarke is key to saving humanity. A wormhole network reveals multiple planets and a final "test" that determines the fate of the species. Most transcend into a higher consciousness, but Clarke and a few others choose to live out their lives on a reborn Earth. == Cast and characters == Eliza Taylor as Clarke Griffin Paige Turco as Abigail "Abby" Griffin (seasons 1–6; guest season 7) Thomas McDonell as Finn Collins (seasons 1–2) Eli Goree as Wells Jaha (season 1; guest season 2) Marie Avgeropoulos as Octavia Blake Bob Morley as Bellamy Blake Kelly Hu as Callie "Cece" Cartwig (season 1) Christopher Larkin as Monty Green (seasons 1–5; guest season 6) Devon Bostick as Jasper Jordan (seasons 1–4) Isaiah Washington as Thelonious Jaha (seasons 1–5) Henry Ian Cusick as Marcus Kane (seasons 1–6) Lindsey Morgan as Raven Reyes (seasons 2–7; recurring season 1) Ricky Whittle as Lincoln (seasons 2–3; recurring season 1) Richard Harmon as John Murphy (seasons 3–7; recurring seasons 1–2) Zach McGowan as Roan (season 4; recurring season 3; guest season 7) Tasya Teles as Echo / Ash (seasons 5–7; guest seasons 2–3; recurring season 4) Shannon Kook as Jordan Green (seasons 6–7; guest season 5) JR Bourne as Russell Lightbourne / Malachi / Sheidheda (season 7; recurring season 6) Chuku Modu as Gabriel Santiago (season 7; recurring season 6) Shelby Flannery as Hope Diyoza (season 7; guest season 6) =

    Read more →
  • Structure mapping engine

    Structure mapping engine

    In artificial intelligence and cognitive science, the structure mapping engine (SME) is an implementation in software of an algorithm for analogical matching based on the psychological theory of Dedre Gentner. The basis of Gentner's structure-mapping idea is that an analogy is a mapping of knowledge from one domain (the base) into another (the target). The structure-mapping engine is a computer simulation of the analogy and similarity comparisons. The theory is useful because it ignores surface features and finds matches between potentially very different things if they have the same representational structure. For example, SME could determine that a pen is like a sponge because both are involved in dispensing liquid, even though they do this very differently. == Structure mapping theory == Structure mapping theory is based on the systematicity principle, which states that connected knowledge is preferred over independent facts. Therefore, the structure mapping engine should ignore isolated source-target mappings unless they are part of a bigger structure. The SME, the theory goes, should map objects that are related to knowledge that has already been mapped. The theory also requires that mappings be done one-to-one, which means that no part of the source description can map to more than one item in the target and no part of the target description can be mapped to more than one part of the source. The theory also requires that if a match maps subject to target, the arguments of subject and target must also be mapped. If both these conditions are met, the mapping is said to be "structurally consistent." == Concepts in SME == SME maps knowledge from a source into a target. SME calls each description a dgroup. Dgroups contain a list of entities and predicates. Entities represent the objects or concepts in a description — such as an input gear or a switch. Predicates are one of three types and are a general way to express knowledge for SME. Relation predicates contain multiple arguments, which can be other predicates or entities. An example relation is: (transmit (what from to)). This relation has a functor transmit and takes three arguments: what, from, and to. Attribute predicates are the properties of an entity. An example of an attribute is (red gear) which means that gear has the attribute red. Function predicates map an entity into another entity or constant. An example of a function is (joules power source) which maps the entity power source onto the numerical quantity joules. Functions and attributes have different meanings, and consequently SME processes them differently. For example, in SME's true analogy rule set, attributes differ from functions because they cannot match unless there is a higher-order match between them. The difference between attributes and functions will be explained further in this section's examples. All predicates have four parameters. They have (1) a functor, which identifies it, and (2) a type, which is either relation, attribute, or function. The other two parameters (3 and 4) are for determining how to process the arguments in the SME algorithm. If the arguments have to be matched in order, commutative is false. If the predicate can take any number of arguments, N-ary is false. An example of a predicate definition is: (sme:defPredicate behavior-set (predicate) relation :n-ary? t :commutative? t) The predicate's functor is “behavior-set,” its type is “relation,” and its n-ary and commutative parameters are both set to true. The “(predicate)” part of the definition specifies that there will be one or more predicates inside an instantiation of behavior-set. == Algorithm details == The algorithm has several steps. The first step of the algorithm is to create a set of match hypotheses between source and target dgroups. A match hypothesis represents a possible mapping between any part of the source and the target. This mapping is controlled by a set of match rules. By changing the match rules, one can change the type of reasoning SME does. For example, one set of match rules may perform a kind of analogy called literal similarity, and another performs a kind of analogy called true-analogy. These rules are not the place where domain-dependent information is added, but rather where the analogy process is tweaked, depending on the type of cognitive function the user is trying to emulate. For a given match rule, there are two types of rules that further define how it will be applied: filter rules and intern rules. Intern rules use only the arguments of the expressions in the match hypotheses that the filter rules identify. This limitation makes the processing more efficient by constraining the number of match hypotheses that are generated. At the same time, it also helps to build the structural consistencies that are needed later on in the algorithm. An example of a filter rule from the true-analogy rule set creates match hypotheses between predicates that have the same functor. The true-analogy rule set has an intern rule that iterates over the arguments of any match hypothesis, creating more match hypotheses if the arguments are entities or functions, or if the arguments are attributes and have the same functor. In order to illustrate how the match rules produce match hypotheses consider these two predicates: transmit torque inputgear secondgear (p1) transmit signal switch div10 (p2) Here we use true analogy for the type of reasoning. The filter match rule generates a match between p1 and p2 because they share the same functor, transmit. The intern rules then produce three more match hypotheses: torque to signal, inputgear to switch, and secondgear to div10. The intern rules created these match hypotheses because all the arguments were entities. If the arguments were functions or attributes instead of entities, the predicates would be expressed as: transmit torque (inputgear gear) (secondgear gear) (p3) transmit signal (switch circuit) (div10 circuit) (p4) These additional predicates make inputgear, secondgear, switch, and div10 functions or attributes depending on the value defined in the language input file. The representation also contains additional entities for gear and circuit. Depending on what type inputgear, secondgear, switch, and div10 are, their meanings change. As attributes, each one is a property of the gear or circuit. For example, the gear has two attributes, inputgear and secondgear. The circuit has two attributes, switch and circuit. As functions inputgear, secondgear, switch, and div10 become quantities of the gear and circuit. In this example, the functions inputgear and secondgear now map to the numerical quantities “torque from inputgear” and “torque from secondgear,” For the circuit the quantities map to logical quantity “switch engaged” and the numerical quantity “current count on the divide by 10 counter.” SME processes these differently. It does not allow attributes to match unless they are part of a higher-order relation, but it does allow functions to match, even if they are not part of such a relation. It allows functions to match because they indirectly refer to entities and thus should be treated like relations that involve no entities. However, as next section shows, the intern rules assign lower weights to matches between functions than to matches between relations. The reason SME does not match attributes is because it is trying to create connected knowledge based on relationships and thus satisfy the systematicity principle. For example, if both a clock and a car have inputgear attributes, SME will not mark them as similar. If it did, it would be making a match between the clock and car based on their appearance — not on the relationships between them. When the additional predicates in p3 and p4 are functions, the results from matching p3 and p4 are similar to the results from p1 and p2 except there is an additional match between gear and circuit and the values for the match hypotheses between (inputgear gear) and (switch circuit), and (secondgear gear) and (div10 circuit), are lower. The next section describes the reason for this in more detail. If the inputgear, secondgear, switch, and div10 are attributes instead of entities, SME does not find matches between any of the attributes. It finds matches only between the transmit predicates and between torque and signal. Additionally, the structural-evaluation scores for the remaining two matches decrease. In order to get the two predicates to match, p3 would need to be replaced by p5, which is demonstrated below. transmit torque (inputgear gear) (div10 gear) (p5) Since the true-analogy rule set identifies that the div10 attributes are the same between p5 and p4 and because the div10 attributes are both part of the higher-relation match between torque and signal, SME makes a match between (div10 gear) and (div10 circuit) — which leads to a match between gear and circuit. Being part of a higher-order match is a requiremen

    Read more →
  • ECML PKDD

    ECML PKDD

    ECML PKDD, the European Conference on Machine Learning Principles and Practice of Knowledge Discovery in Databases, is one of the leading academic conferences on machine learning and knowledge discovery, held in Europe every year. == History == ECML PKDD is a merger of two European conferences, European Conference on Machine Learning (ECML) and European Conference on Principles and Practice of Knowledge Discovery in Databases (PKDD). ECML and PKDD have been co-located since 2001; however, both ECML and PKDD retained their own identity until 2007. For example, the 2007 conference was known as "the 18th European Conference on Machine Learning (ECML) and the 11th European Conference on Principles and Practice of Knowledge Discovery in Databases (PKDD)", or in brief, "ECML/PKDD 2007", and both ECML and PKDD had their own conference proceedings. In 2008 the conferences were merged into one conference, and the division into traditional ECML topics and traditional PKDD topics was removed. The history of ECML dates back to 1986, when the European Working Session on Learning was first held. In 1993 the name of the conference was changed to European Conference on Machine Learning. PKDD was first organised in 1997. Originally PKDD stood for the European Symposium on Principles of Data Mining and Knowledge Discovery from Databases. The name European Conference on Principles and Practice of Knowledge Discovery in Databases was used since 1999. The conference remains highly competitive, consistently maintaining an average acceptance rate of around 25% for the main research track. == Upcoming conferences == == List of past conferences ==

    Read more →
  • PowerBuilder

    PowerBuilder

    PowerBuilder is an integrated development environment owned by SAP since the acquisition of Sybase in 2010. On July 5, 2016, SAP and Appeon entered into an agreement whereby Appeon, an independent company, would be responsible for developing, selling, and supporting PowerBuilder. Over the years, PowerBuilder has been updated with new standards. In 2010, a major upgrade of PowerBuilder was released to provide support for the Microsoft .NET Framework. In 2014, support was added for OData, dockable windows, and 64-bit native applications. In 2019 support was added for rapidly creating RESTful Web APIs and non-visual .NET assemblies using the C# language and the .NET Core framework. And PowerScript client app development was revamped with new UI technologies and cloud architecture. In 2025 the IDE was revamped with new code editor and ultra-fast compiler. Appeon has been releasing new features every 6-12 month cycles, which per the product roadmap focus on four key focus areas: sustaining core features, modernizing application UI, improving developer productivity, and incorporating more Cloud technology. == Features == PowerBuilder has a native data-handling component called a DataWindow, which can be used to create, edit, and display data from a database. This object gives the programmer a number of tools for specifying and controlling user interface appearance and behavior, and also provides simplified access to database content and JSON or XML from Web services. To some extent, the DataWindow frees the programmer from considering the differences between Database Management Systems from different vendors. DataWindow can display data using multiple presentation styles and can connect to various data sources. == Usage == PowerBuilder is used primarily for building business-oriented CRUD applications. Although new software products are rarely built with PowerBuilder, many client-server ERP products and line-of-business applications built in the late 1980s to early 2000s with PowerBuilder still provide core database functions for large enterprises in government, higher education, manufacturing, insurance, banking, energy, and telecommunications. == History == === Early history === PowerBuilder originated from Computer Solutions Inc. (CSI), a software consulting firm founded in 1974 by Mitchell Kertzman in Massachusetts. CSI developed GrowthPower, an MRP II software package with integrated financial modules released in 1981, which ran exclusively on the HP 3000 platform and achieved over 1,000 customer installations at its peak. In the late 1980s, as demand increased for graphical user interfaces amid the rise of Microsoft Windows, Kertzman partnered with Dave Litwack, former executive vice president of product development at Cullinet Software (acquired by Computer Associates in 1989). Litwack joined the company in 1988 as head of research and development to develop a client/server GUI tool, leading to its rebranding as Powersoft Corporation in 1990. PowerBuilder 1.0 was released in July 1991 as a rapid application development tool featuring the DataWindow and PowerScript language. Powersoft went public on February 3, 1993, with shares closing at $38 from an initial $20 price. Sybase announced its acquisition of Powersoft on November 15, 1994, in a stock swap valued at approximately $940 million; the merger closed on February 14, 1995, at a revised value of about $904 million due to Sybase's stock fluctuations. === Recent history === In December 2013 SAP announced the new version going directly to number 15 and released a beta version. Key features included support for the .NET Framework v4.5, SQL Server 2012, Oracle 12, Windows 8, OData and Dockable Windows. SAP later released this as version 12.6. On May 31, 2019, PowerBuilder 2019 was released by Appeon. This release supports C# development. It provides a new C# IDE, .NET data access objects, C# migration solution, Web API client, and UI themes. On April 3, 2020, PowerBuilder 2019 R2 was launched by Appeon. This release includes a first-ever PowerScript-to-C# code converter, which can automatically migrate 80-95% of PowerBuilder business logic and DataWindows to C#. Interoperability between PowerScript and .NET programming languages is also now supported. Many existing features have also been enhanced. On January 22, 2021, PowerBuilder 2019 R3 was launched by Appeon. This release provides a groundbreaking new app deployment technology called PowerClient, which securely automates the installation and update of client apps over HTTPS. C# Web API development has been greatly enhanced with asynchronous programming and support for Amazon Aurora and Azure cloud databases. Aside from many other new features, PowerBuilder 2019 R3 is a long-term support (LTS) version that replaces previous LTS versions On August 6, 2021, PowerBuilder 2021 was launched by Appeon. The Cloud deployment capability of the PowerBuilder 2021 IDE, in conjunction with the matching PowerServer 2021 runtime, was revamped, bringing PowerBuilder up-to-date with the latest .NET technologies. The presentation layer now executes PowerScript natively on Windows devices. The middle-tier has been rebuilt around REST API standard with a pure .NET Core implementation. A new CI/CD utility that integrates with Git/SVN and Jenkins, witch compiles all PowerBuilder projects using the command-line interface, was added alongside other features. On September 4, 2022, PowerBuilder 2022 was launched by Appeon. This release brings enhancements to the productivity of developing both client/server & installable cloud apps and more security measures to safeguard your apps. It includes many new features, including Windows 11 support, introducing time-saving functionalities to the IDE, such as Tabbed Code Editor, Jump to Objects, and Quick Code Search, and supports the latest HTTP/2 and TLS 1.3 protocols and two-way TLS authentication. On August 4, 2023, PowerBuilder 2022 R2 was launched by Appeon. This release introduces a range of new features aimed at helping developers build powerful, feature-rich, and secure client/server and installable cloud apps more efficiently, including tabbed windows, fillable PDFs, and SMTP client. On January 8, 2024, PowerBuilder 2022 R3 was launched by Appeon. This release is a long-term support version. Features previously released in earlier releases have been enhanced and/or corrected. On May 7, 2025, PowerBuilder 2025 was launched by Appeon. This release delivers a revamped IDE that boosts developer productivity throughout the SLDC—from writing and extending code to debugging, automating builds, and deploying applications. It features a new-generation code editor, ultra-fast compiler, automatic REST API creation, faster GIT operations, and codeless UI modernization features. == Features == PowerBuilder is an object-oriented programming language. Nearly all of the visual and non-visual objects support inheritance, polymorphism, and encapsulation. The programmer may utilize a common code framework such as PowerBuilder Foundation Classes, also known as PFC, to inherit objects from and leverage pre-existing code. The DataWindow is the key component (and selling point) of PowerBuilder. The DataWindow offers a visual SQL painter which supports outer joins, unions and subquery operations. It can convert SQL to visual representation and back, so the developer can use native SQL if desired. DataWindow updates are automatic — it produces the proper SQL at runtime based on the DBMS to which the user is currently connected. This feature makes it easier for developers who are not experienced with SQL. The DataWindow also has the built-in ability to both retrieve data and update data via stored procedures or REST Web APIs as well as import/export JSON data. The RESTClient object introduced in PowerBuilder 2017 facilitates bridging the DataWindow with REST Web APIs and requiring minimal coding. === RDBMS interfaces === PowerBuilder offers native interfaces to all major databases, as well as ODBC and OLE-DB, in the Enterprise version. There are many connectivity options that allow performance monitoring and tuning, such as: Integrated security Tracing of all SQL Isolation level Password expiration dialog Blocking factor Number of SQL statements to cache Use connection pool Thread safety Trace ODBC API calls Due to the information about the database schema (such as primary key information) that are stored in PowerBuilder's data dictionary, the code required to implement data display and browsing is greatly simplified, because the dictionary information allows generation of the appropriate SQL behind the scenes. PowerBuilder supports the following ways of interacting with a database: DataWindow this is the simplest approach, relying on automatically generated SQL. Embedded SQL Embedded SQL supports SELECT, INSERT, UPDATE, DELETE and cursors. This option is used when the developer desires more control than is available with the

    Read more →
  • Digital organism

    Digital organism

    A digital organism is a self-replicating computer program that mutates and evolves. Digital organisms are used as a tool to study the dynamics of Darwinian evolution, and to test or verify specific hypotheses or mathematical models of evolution. The study of digital organisms is closely related to the area of artificial life. == History == Digital organisms can be traced back to the game Darwin, developed in 1961 at Bell Labs, in which computer programs had to compete with each other by trying to stop others from executing . A similar implementation that followed this was the game Core War. In Core War, it turned out that one of the winning strategies was to replicate as fast as possible, which deprived the opponent of all computational resources. Programs in the Core War game were also able to mutate themselves and each other by overwriting instructions in the simulated "memory" in which the game took place. This allowed competing programs to embed damaging instructions in each other that caused errors (terminating the process that read it), "enslaved processes" (making an enemy program work for you), or even change strategies mid-game and heal themselves. Steen Rasmussen at Los Alamos National Laboratory took the idea from Core War one step further in his core world system by introducing a genetic algorithm that automatically wrote programs. However, Rasmussen did not observe the evolution of complex and stable programs. It turned out that the programming language in which core world programs were written was very brittle, and more often than not mutations would completely destroy the functionality of a program. The first to solve the issue of program brittleness was Thomas S. Ray with his Tierra system, which was similar to core world. Ray made some key changes to the programming language such that mutations were much less likely to destroy a program. With these modifications, he observed for the first time computer programs that did indeed evolve in a meaningful and complex way. Later, Chris Adami, Titus Brown, and Charles Ofria started developing their Avida system, which was inspired by Tierra but again had some crucial differences. In Tierra, all programs lived in the same address space and could potentially execute or otherwise interfere with each other's code. In Avida, on the other hand, each program lives in its own address space. Because of this modification, experiments with Avida became much cleaner and easier to interpret than those with Tierra. With Avida, digital organism research has begun to be accepted as a valid contribution to evolutionary biology by a growing number of evolutionary biologists. Evolutionary biologist Richard Lenski of Michigan State University has used Avida extensively in his work. Lenski, Adami, and their colleagues have published in journals such as Nature and the Proceedings of the National Academy of Sciences (USA). In 1996, Andy Pargellis created a Tierra-like system called Amoeba that evolved self-replication from a randomly seeded initial condition. More recently REvoSim - a software package based around binary digital organisms - has allowed evolutionary simulations of large populations that can be run for geological timescales.

    Read more →
  • IJCAI Award for Research Excellence

    IJCAI Award for Research Excellence

    The IJCAI Award for Research Excellence is a biannual award before given at the IJCAI conference to researcher in artificial intelligence as a recognition of excellence of their career. Beginning in 2016, the conference is held annually and so is the award. == Laureates == The recipients of this award have been: John McCarthy (1985) Allen Newell (1989) Marvin Minsky (1991) Raymond Reiter (1993) Herbert A. Simon (1995) Aravind Joshi (1997) Judea Pearl (1999) Donald Michie (2001) Nils Nilsson (2003) Geoffrey E. Hinton (2005) Alan Bundy (2007) Victor R. Lesser (2009) Robert Kowalski (2011) Hector Levesque (2013) Barbara Grosz (2015) for her pioneering research in Natural Language Processing and in theories and applications of Multiagent Collaboration. Michael I. Jordan (2016) for his groundbreaking and impactful research in both the theory and application of statistical machine learning. Andrew Barto (2017) for his pioneering work in the theory of reinforcement learning. Jitendra Malik (2018) Yoav Shoham (2019) Eugene Freuder (2020) Richard S. Sutton (2021) Stuart J. Russell (2022) Sarit Kraus (2023) for her pioneering work of the study of interactions among self-interested agents, creating the field of automated negotiation, and developing methods for coalition formation and teamwork, both as formal models and real-world implementations. == Winners of also Turing Award == John McCarthy (1971) Allen Newell (1975) Marvin Minsky (1969) Herbert A. Simon (1975) Judea Pearl (2011) Geoffrey Hinton (2018) Andrew Barto (2024) Richard S. Sutton (2024)

    Read more →